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
the CVE-2023-2976 reported for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed.
Current behavior
the CVE-2023-2976 reported for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed.
Xray will report the CVE-2023-2976 for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed as shown below:
Expected behavior
Build-info-extractor-maven3-2.40.0-uber.jar should not be vulnerable. If the above CVE gets fixed, there will be no violations.
JFrog CLI version
2.46.2
Operating system type and version
Rhel 8
JFrog Artifactory version
latest
JFrog Xray version
latest
The text was updated successfully, but these errors were encountered:
Describe the bug
the CVE-2023-2976 reported for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed.
Current behavior
the CVE-2023-2976 reported for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed.
Reproduction steps
Download the package build-info-extractor-maven3-2.40.0-uber.jar provided by JFrog and scan it with the help of Xray.
Xray will report the CVE-2023-2976 for the component "com.google.guava:guava" used in the "build-info-extractor-maven3-2.40.0-uber.jar" file which needs to be fixed as shown below:
Expected behavior
Build-info-extractor-maven3-2.40.0-uber.jar should not be vulnerable. If the above CVE gets fixed, there will be no violations.
JFrog CLI version
2.46.2
Operating system type and version
Rhel 8
JFrog Artifactory version
latest
JFrog Xray version
latest
The text was updated successfully, but these errors were encountered: