tabacmend-up / Webgoat

Other
0 stars 0 forks source link

jose4j-0.7.6.jar: 3 vulnerabilities (highest severity is: 8.2) reachable #34

Open mend-for-github-com[bot] opened 1 year ago

mend-for-github-com[bot] commented 1 year ago
Vulnerable Library - jose4j-0.7.6.jar

The jose.4.j library is a robust and easy to use open source implementation of JSON Web Token (JWT) and the JOSE specification suite (JWS, JWE, and JWK). It is written in Java and relies solely on the JCA APIs for cryptography. Please see https://bitbucket.org/b_c/jose4j/wiki/Home for more info, examples, etc..

Library home page: https://bitbucket.org/b_c/jose4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bitbucket/b_c/jose4j/0.7.6/jose4j-0.7.6.jar

Vulnerabilities

CVE Severity CVSS Exploit Maturity EPSS Dependency Type Fixed in (jose4j version) Remediation Possible** Reachability
CVE-2023-51775 High 7.1 Not Defined 0.0% jose4j-0.7.6.jar Direct 0.9.4

Reachable

CVE-2023-31582 High 8.2 Not Defined 0.1% jose4j-0.7.6.jar Direct 0.9.3
WS-2023-0116 Medium 6.9 Not Defined jose4j-0.7.6.jar Direct 0.9.3

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2023-51775 ### Vulnerable Library - jose4j-0.7.6.jar

The jose.4.j library is a robust and easy to use open source implementation of JSON Web Token (JWT) and the JOSE specification suite (JWS, JWE, and JWK). It is written in Java and relies solely on the JCA APIs for cryptography. Please see https://bitbucket.org/b_c/jose4j/wiki/Home for more info, examples, etc..

Library home page: https://bitbucket.org/b_c/jose4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bitbucket/b_c/jose4j/0.7.6/jose4j-0.7.6.jar

Dependency Hierarchy: - :x: **jose4j-0.7.6.jar** (Vulnerable Library)

Found in base branches: main, log4j

### Reachability Analysis This vulnerability is potentially reachable ``` org.owasp.webgoat.webwolf.jwt.JWTToken (Application) -> org.jose4j.jwt.consumer.JwtConsumer (Extension) -> ❌ org.jose4j.jwe.JsonWebEncryption (Vulnerable Component) ```

### Vulnerability Details

The jose4j component before 0.9.4 for Java allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.

Publish Date: 2023-12-25

URL: CVE-2023-51775

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

### CVSS 4 Score Details (7.1)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS4 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2023-51775

Release Date: 2023-12-25

Fix Resolution: 0.9.4

In order to enable automatic remediation, please create workflow rules

CVE-2023-31582 ### Vulnerable Library - jose4j-0.7.6.jar

The jose.4.j library is a robust and easy to use open source implementation of JSON Web Token (JWT) and the JOSE specification suite (JWS, JWE, and JWK). It is written in Java and relies solely on the JCA APIs for cryptography. Please see https://bitbucket.org/b_c/jose4j/wiki/Home for more info, examples, etc..

Library home page: https://bitbucket.org/b_c/jose4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bitbucket/b_c/jose4j/0.7.6/jose4j-0.7.6.jar

Dependency Hierarchy: - :x: **jose4j-0.7.6.jar** (Vulnerable Library)

Found in base branch: log4j

### Vulnerability Details

jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less.

Publish Date: 2023-10-24

URL: CVE-2023-31582

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.1%

### CVSS 4 Score Details (8.2)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS4 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://bitbucket.org/b_c/jose4j/issues/203/insecure-support-of-setting-pbe-less-then

Release Date: 2023-10-24

Fix Resolution: 0.9.3

In order to enable automatic remediation, please create workflow rules

WS-2023-0116 ### Vulnerable Library - jose4j-0.7.6.jar

The jose.4.j library is a robust and easy to use open source implementation of JSON Web Token (JWT) and the JOSE specification suite (JWS, JWE, and JWK). It is written in Java and relies solely on the JCA APIs for cryptography. Please see https://bitbucket.org/b_c/jose4j/wiki/Home for more info, examples, etc..

Library home page: https://bitbucket.org/b_c/jose4j/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bitbucket/b_c/jose4j/0.7.6/jose4j-0.7.6.jar

Dependency Hierarchy: - :x: **jose4j-0.7.6.jar** (Vulnerable Library)

Found in base branch: log4j

### Vulnerability Details

RSA1_5 in jose4j is susceptible to chosen ciphertext attacks. The attack allows to decrypt RSA1_5 or RSA_OAEP encrypted ciphertexts. It may be feasible to sign with affected keys.

Publish Date: 2023-04-27

URL: WS-2023-0116

### Threat Assessment

Exploit Maturity: Not Defined

EPSS:

### CVSS 4 Score Details (6.9)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS4 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-jgvc-jfgh-rjvv

Release Date: 2023-04-27

Fix Resolution: 0.9.3

In order to enable automatic remediation, please create workflow rules


In order to enable automatic remediation for this issue, please create workflow rules