You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2018. It is now read-only.
A public user who tries to view a private announcement will get a 404.
However if it tries to delete a private anouncement it will get served a 403 error (Forbidden)
In that case it will know that there somehow is an announcement carrying that id.
The text was updated successfully, but these errors were encountered:
This is not really a security issue as an api inconsistency, sometimes you'll get a 404, sometimes a 403 depending on the method used for permission checking (dynamic in database vs dynamic in python vs static)
ajrouvoet
changed the title
Public users can indirectly find announcements
API inconcistent in returning 404/403 depending on permission check used
Jul 11, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A public user who tries to view a private announcement will get a 404.
However if it tries to delete a private anouncement it will get served a 403 error (Forbidden)
In that case it will know that there somehow is an announcement carrying that id.
The text was updated successfully, but these errors were encountered: