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
Path to dependency file: /webgoat-integration-tests/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar
Path to dependency file: /webgoat-integration-tests/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar
Dependency Hierarchy:
❌ jjwt-0.7.0.jar (Vulnerable Library)
Found in base branch: add_test_clientside_filtering
Vulnerability Details
JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class. NOTE: the vendor disputes this because the "ignores" behavior cannot occur (in any version) unless there is a user error in how JJWT is used, and because the version that was actually tested must have been more than six years out of date.
Vulnerable Library - jjwt-0.7.0.jar
Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Library home page: http://nexus.sonatype.org/oss-repository-hosting.html/jjwt
Path to dependency file: /webgoat-integration-tests/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-31033
Vulnerable Library - jjwt-0.7.0.jar
Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Library home page: http://nexus.sonatype.org/oss-repository-hosting.html/jjwt
Path to dependency file: /webgoat-integration-tests/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar,/home/wss-scanner/.m2/repository/io/jsonwebtoken/jjwt/0.7.0/jjwt-0.7.0.jar
Dependency Hierarchy:
Found in base branch: add_test_clientside_filtering
Vulnerability Details
JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class. NOTE: the vendor disputes this because the "ignores" behavior cannot occur (in any version) unless there is a user error in how JJWT is used, and because the version that was actually tested must have been more than six years out of date.
Publish Date: 2024-04-01
URL: CVE-2024-31033
CVSS 2 Score Details (0.0)
Base Score Metrics not available
The text was updated successfully, but these errors were encountered: