DependencyTrack / DependencyTrack/dependency-track

false postive delected by dependency track

Open
#3,820 1 comment 0 reactions 0 assignees View on GitHub
FP/FN report
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### Current Behavior

![Capture](https://github.com/DependencyTrack/dependency-track/assets/92458532/b9fec741-c2c2-4757-82cd-f9ced0e1a751)
![Capture](https://github.com/DependencyTrack/dependency-track/assets/92458532/06fc78b4-9562-441b-ac9f-2df4582b2b19)

### Steps to Reproduce

Upon generating the Software Bill of Materials (SBOM) using cdxgen v8.6.0 and uploading it for analysis, the component spring-security-crypto version 5.8.12 was flagged as vulnerable under CVE-2020-5408 in the audit vulnerabilities section.

Details of the Issue:
Component: spring-security-crypto
Version: 5.8.12
CVE ID: CVE-2020-5408
CVE-2020-5408 Description:
Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16, and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor. A malicious user with access to the data encrypted using such an encryptor may be able to derive the unencrypted values using a dictionary attack.

Issue:
There is no mention of version 5.8.x being affected by this vulnerability in the CVE details. Additionally, I verified on Maven Repository, and there are no vulnerabilities listed for version 5.8.12.

Request:
I would like to request a review of this detection to ensure the accuracy of the vulnerability data. If this is a false positive, it would be helpful to correct the detection rules to prevent similar issues in the future.

### Expected Behavior

the component is not vulnerable and should not be flagged as vulnerable

### Dependency-Track Version

4.10.x

### Dependency-Track Distribution

Executable WAR

### Database Server

PostgreSQL

### Database Server Version

15

### Browser

Google Chrome

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the report with an SBOM generated by cdxgen v8.6.0 and inspect the audit vulnerabilities result for spring-security-crypto 5.8.12 and CVE-2020-5408. Review the vulnerability data and matching behavior involved in that result; done means the component is no longer flagged while genuinely affected versions remain detectable.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, postgresql
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.