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

No Anti-CSRF tokens generated for unregistered users / any user profile accessible by all anonymous users #45

Open
overcrash66 opened this issue Sep 30, 2019 · 1 comment
Assignees
Labels
Milestone

Comments

@overcrash66
Copy link

Expected Behaviour: CSRF protection enabled everything.

Actual Behaviour: No Anti-CSRF tokens generated for unregistered users / any user profile accessible by all anonymous users

Steps to Reproduce Issue

No Anti-CSRF tokens were found in a HTML submission form.
A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.

CSRF attacks are effective in a number of situations, including:
* The victim has an active session on the target site.
* The victim is authenticated via HTTP auth on the target site.
* The victim is on the same local network as the target site.

CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

Server Environment (PHP, MySQL, Apache Version and Operating System): Current version

@AndyRixon AndyRixon self-assigned this Nov 7, 2019
@AndyRixon AndyRixon added the bug label Nov 7, 2019
@AndyRixon AndyRixon added this to the 1.1.4 milestone Nov 7, 2019
@AndyRixon
Copy link
Owner

Will get that changed so only logged in users can see user profiles.

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