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.

Sign up for GitHub

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

Jump to bottom

SSRF as it's own top-category #354

Closed
fennellkyle opened this issue May 11, 2023 · 2 comments
Closed

SSRF as it's own top-category #354

fennellkyle opened this issue May 11, 2023 · 2 comments

Comments

@fennellkyle
Copy link

I've been thinking about this for a bit.
SSRF is nested under the Broken Access Control category.
While SSRF can result from Broken Access Controls, it's not the not common cause of this vulnerability. The most common causes I've seen are the result of inadequate input validation and sanitization. Sometimes there are no issues with access controls.

I'm wondering if anyone else thinks SSRF should be it's own top-level category, similar to XSS?
@TimmyBugcrowd
Copy link
Contributor

I think this is a good idea. We'll discuss it with the team but from my side, I think this is a change we can do in the next VRT release.

@amalmurali47 amalmurali47 mentioned this issue Jun 21, 2023
Open
@TimmyBugcrowd
Copy link
Contributor

PR #359 has been submitted, hence closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fennellkyle @TimmyBugcrowd