You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have recently observed an issue where DependencyCheck reported many CVEs after upgraded from Java8 to Java17 and renamed a JAR file to "utaruntime-2.0.0-bld13.0.80.jar".
The following test was done to isolate the issue:
With Java8:
- Original filename - no issue was reported
- Renamed jar file - no issue was reported
With Java17:
- Original filename - no issue was reported
- Renamed jar file - issue was reported
The issue is only observed with Java17 and JAR file renamed.
Please help us to understand what could cause the issue.
Thank you very much in advance for your assistance.
The text was updated successfully, but these errors were encountered:
Description
I see above vulnerabilties in java17 version when artifcatid in pom is not same as jar name. Above CVE are reported on java 17 version of jar. No issue is found in java 8 version of same jar
We have recently observed an issue where DependencyCheck reported many CVEs after upgraded from Java8 to Java17 and renamed a JAR file to "utaruntime-2.0.0-bld13.0.80.jar".
The following test was done to isolate the issue:
With Java8:
- Original filename - no issue was reported
- Renamed jar file - no issue was reported
With Java17:
- Original filename - no issue was reported
- Renamed jar file - issue was reported
The issue is only observed with Java17 and JAR file renamed.
Please help us to understand what could cause the issue.
Thank you very much in advance for your assistance.
The text was updated successfully, but these errors were encountered: