DependencyTrack / DependencyTrack/dependency-track
Automatic suppresions for vulnerability aliases
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Currently, when I suppress a vulnerability/apply a VEX file in a project in DT v5, the suppression is not applied also for aliases of that vulnerability. For example, if suppression is applied to a vulnerability identified by a CVE number, but the vulnerability also have a GitHub identifier, the later one is not suppressed as well.
### Proposed Behavior
When I suppress a vulnerability, I expect also the aliases to be suppressed automatically.
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/main/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this enhancement was already requested
Contributor guide
Research direction
Start by tracing how vulnerability suppressions and VEX files are applied in Dependency-Track, then inspect how vulnerability aliases are represented and resolved. Add coverage for a vulnerability identified by one identifier with an additional GitHub alias, and verify that suppressing the vulnerability also suppresses its aliases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100