We are now getting false positives on cpe:2.3:a:netty:netty:2.1.8:*:*:*:*:*:*:* and cpe:2.3:a:netty:netty:0.8.11:*:*:*:*:*:*:* that we weren't getting before.
spring-boot-starter-reactor-netty-2.1.8.RELEASE.jar (pkg:maven/org.springframework.boot/[email protected], cpe:2.3:a:netty:netty:2.1.8:*:*:*:*:*:*:*) : CVE-2014-3488, CVE-2015-2156, CVE-2019-16869
reactor-netty-0.8.11.RELEASE.jar (pkg:maven/io.projectreactor.netty/[email protected], cpe:2.3:a:netty:netty:0.8.11:*:*:*:*:*:*:*) : CVE-2014-3488, CVE-2015-2156, CVE-2019-16869
False positive on library spring-boot-starter-reactor-netty-2.1.8.RELEASE.jar - reported as cpe:2.3:a:netty:netty:2.1.8:*:*:*:*:*:*:*
False positive on library reactor-netty-0.8.11.RELEASE.jar - reported as cpe:2.3:a:netty:netty:0.8.11:*:*:*:*:*:*:*
plugins {
id 'java'
id 'org.springframework.boot' version '2.1.8.RELEASE'
id 'io.spring.dependency-management' version '1.0.8.RELEASE'
id 'org.owasp.dependencycheck' version '5.2.2'
}
//...
// Bump Netty to address https://nvd.nist.gov/vuln/detail/CVE-2019-16869
ext['netty.version'] = '4.1.42.Final'
dependencies {
implementation 'org.springframework.boot:spring-boot-starter-reactor-netty:2.1.8.RELEASE'
}
OK, I think it's to do with the 30 Sep CPE deprecation remaps in
https://nvd.nist.gov/vuln/detail/CVE-2014-3488#VulnChangeHistorySection
https://nvd.nist.gov/vuln/detail/CVE-2015-2156#VulnChangeHistorySection
https://nvd.nist.gov/vuln/detail/CVE-2019-16869VulnChangeHistorySection
The previous FP suppressions baked into OWASP dependency check for netty_project need to be updated to netty I think; and may need to be expanded as perhaps more FPs will be incoming with the more generic names here :-(
Same happens with netty-reactive-streams-2.0.3.jar and async-http-client-netty-utils-2.10.3.jar.
For example, in async-http-client-netty-utils cpe:2.3:a:netty:netty:2.10.3:*:*:*:*:*:*:*; which triggers the false positive.
@chadlwilson thank you for identifying the issue with the suppression rule for netty. I have updated this and it will be included in the next release.
Most helpful comment
@chadlwilson thank you for identifying the issue with the suppression rule for netty. I have updated this and it will be included in the next release.