Jason-Clark-FG/OpenMetadata-FG

oidc-client-1.11.5.tgz: 1 vulnerabilities (highest severity is: 9.1) - autoclosed

Closed this issue · 1 comments

Vulnerable Library - oidc-client-1.11.5.tgz

Path to dependency file: /openmetadata-ui/src/main/resources/ui/package.json

Path to vulnerable library: /openmetadata-ui/src/main/resources/ui/node_modules/crypto-js/package.json

Found in HEAD commit: 0d43a8050e6c73014cff9be7dec96a81296f3061

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (oidc-client version) Remediation Possible**
CVE-2023-46233 Critical 9.1 crypto-js-4.1.1.tgz Transitive N/A*

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

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

Details

CVE-2023-46233

Vulnerable Library - crypto-js-4.1.1.tgz

JavaScript library of crypto standards.

Library home page: https://registry.npmjs.org/crypto-js/-/crypto-js-4.1.1.tgz

Path to dependency file: /openmetadata-ui/src/main/resources/ui/package.json

Path to vulnerable library: /openmetadata-ui/src/main/resources/ui/node_modules/crypto-js/package.json

Dependency Hierarchy:

  • oidc-client-1.11.5.tgz (Root Library)
    • crypto-js-4.1.1.tgz (Vulnerable Library)

Found in HEAD commit: 0d43a8050e6c73014cff9be7dec96a81296f3061

Found in base branch: main

Vulnerability Details

crypto-js is a JavaScript library of crypto standards. Prior to version 4.2.0, crypto-js PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 4.2.0 contains a patch for this issue. As a workaround, configure crypto-js to use SHA256 with at least 250,000 iterations.

Publish Date: 2023-10-25

URL: CVE-2023-46233

CVSS 3 Score Details (9.1)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

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

Release Date: 2023-10-25

Fix Resolution: crypto-js - 4.2.0

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.