Open OrangeDog opened 8 months ago
Maven Coordinates
<dependency>
<groupId>com.querydsl</groupId>
<artifactId>querydsl-core</artifactId>
<version>5.0.0</version>
</dependency>
Suppression rule:
<suppress base="true">
<notes><![CDATA[
FP per issue #6467
]]></notes>
<packageUrl regex="true">^pkg:maven/com\.querydsl/querydsl-core@.*$</packageUrl>
<cpe>cpe:/a:homepage_project:homepage</cpe>
</suppress>
Link to test results: https://github.com/jeremylong/DependencyCheck/actions/runs/7902690410
Package URl
pkg:maven/com.querydsl/querydsl-core@5.0.0
CPE
cpe:2.3:a:homepage_project:homepage:5.0.0:::::::*
CVE
No response
ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
9.0.9
Description
When POMs do not have their properties expanded correctly, dependency check still uses the variable as evidence. In an apparently common case, this leads to this evidence:
and a detection of
cpe:2.3:a:homepage_project:homepage
.Rather than have to individually suppress this whenever it comes up, perhaps the analyser should simply discard any evidence that is a Maven property expression?