Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sikkerhetsproblem med require_god #2

Open
simen opened this issue Dec 14, 2011 · 4 comments
Open

Sikkerhetsproblem med require_god #2

simen opened this issue Dec 14, 2011 · 4 comments
Labels

Comments

@simen
Copy link
Member

simen commented Dec 14, 2011

require_god har et stort sikkerhetsproblem nå ettersom de ikke sjekker at ressursen og brukeren hører til samme realm. Det gir i praksis alle guder mulighet til å laste alle ressurser i systemet.

@ghost ghost assigned kytrinyx Mar 7, 2012
@kytrinyx
Copy link
Contributor

I started looking into this, and we can't just assume that the request.host is going to map to the realm, because people can make requests to a different host.

We actually need to verify against the resource(s) that are being fetched, and we won't know this until we've actually fetched the resource.

I don't see how we can implement the realm check in require_god and require_identity

@simen
Copy link
Member Author

simen commented Nov 26, 2012

No, but wouldn't the correct way to do this be passing the expected realm to require_god?

def require_god(realm = nil)

And log a warning if realm is not provided?

@simen
Copy link
Member Author

simen commented Nov 26, 2012

Also we should provide a current_realm method that is heavily cached (by request host) and uses checkpoint to determine realm.

@kytrinyx
Copy link
Contributor

Cool, that makes sense.

@kytrinyx kytrinyx removed their assignment Aug 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants