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

Enhance badge API to require authorization #3596

Open
2 tasks done
SaberStrat opened this issue Apr 2, 2024 · 1 comment
Open
2 tasks done

Enhance badge API to require authorization #3596

SaberStrat opened this issue Apr 2, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@SaberStrat
Copy link

Current Behavior

As of Dependency-Track v4.10.1, Badges can only be activated globally for all projects and versions and the GETs do not require authorization.

Proposed Behavior

I'm proposing basically what @stevespringett suggested here as a future enhancement of the current badges implementation: #252 (comment):
implement a new permission to control access to the badge API. Together with Portfolio Access Control, this would allow for a convenient way to control access on a project basis.

While convenient as a feature, and allowing any downstream stakeholder to display the state of vulnerabilities and violations about a tracked project, activating badges in the current implementation opens up a hole in the security for any attacker to use with knowledge of project names or versions. They can fetch quite a lot of data about a project from that API that way that would otherwise require authorization.

Checklist

@SaberStrat SaberStrat added the enhancement New feature or request label Apr 2, 2024
@SaberStrat
Copy link
Author

I could have a look at this myself--unless this is already in the works as part of some other change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant