Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm-check-updates-16.3.19.tgz: 1 vulnerabilities (highest severity is: 5.3) #475

Open
mend-for-github-com bot opened this issue Jul 15, 2024 · 3 comments
Labels
Mend: dependency security vulnerability Security vulnerability detected by Mend

Comments

@mend-for-github-com
Copy link
Contributor

mend-for-github-com bot commented Jul 15, 2024

Vulnerable Library - npm-check-updates-16.3.19.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Found in HEAD commit: d672a8e906d9cd8aa604be3e37584301f4219b81

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (npm-check-updates version) Remediation Possible**
CVE-2024-4067 Medium 5.3 micromatch-4.0.7.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-2024-4067

Vulnerable Library - micromatch-4.0.7.tgz

Library home page: https://registry.npmjs.org/micromatch/-/micromatch-4.0.7.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • npm-check-updates-16.3.19.tgz (Root Library)
    • globby-11.0.4.tgz
      • fast-glob-3.2.7.tgz
        • micromatch-4.0.7.tgz (Vulnerable Library)

Found in HEAD commit: d672a8e906d9cd8aa604be3e37584301f4219b81

Found in base branch: main

Vulnerability Details

The NPM package micromatch prior to 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching. This issue was fixed in version 4.0.8.
Mend Note: After conducting a further research, it was concluded that CVE-2024-4067 should not reflect the security risk score in NVD, but will be kept for users' awareness.

Publish Date: 2024-05-13

URL: CVE-2024-4067

CVSS 3 Score Details (5.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2024-05-13

Fix Resolution: micromatch - 4.0.8

@mend-for-github-com mend-for-github-com bot added the Mend: dependency security vulnerability Security vulnerability detected by Mend label Jul 15, 2024
@github-actions github-actions bot added the untriaged Issues that have not yet been triaged label Jul 15, 2024
@mend-for-github-com mend-for-github-com bot changed the title npm-check-updates-16.3.19.tgz: 2 vulnerabilities (highest severity is: 7.5) npm-check-updates-16.3.19.tgz: 2 vulnerabilities (highest severity is: 7.5) - autoclosed Jul 16, 2024
Copy link
Contributor Author

✔️ 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.

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Engineering Effectiveness Board Jul 16, 2024
@gaiksaya gaiksaya removed the untriaged Issues that have not yet been triaged label Aug 15, 2024
@mend-for-github-com mend-for-github-com bot changed the title npm-check-updates-16.3.19.tgz: 2 vulnerabilities (highest severity is: 7.5) - autoclosed npm-check-updates-16.3.19.tgz: 1 vulnerabilities (highest severity is: 5.3) Nov 20, 2024
@mend-for-github-com mend-for-github-com bot reopened this Nov 20, 2024
Copy link
Contributor Author

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

@github-project-automation github-project-automation bot moved this from ✅ Done to 🏗 In progress in Engineering Effectiveness Board Nov 20, 2024
@github-actions github-actions bot added the untriaged Issues that have not yet been triaged label Nov 20, 2024
@dblock dblock removed the untriaged Issues that have not yet been triaged label Nov 25, 2024
@dblock
Copy link
Member

dblock commented Nov 25, 2024

[Catch All Triage - 1, 2, 3, 4]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by Mend
Projects
Status: 🏗 In progress
Development

No branches or pull requests

2 participants