CVE-2021-33587 (High) detected in css-what-3.4.2.tgz

[mend-bolt-for-github]

CVE-2021-33587 - High Severity Vulnerability

Vulnerable Library - css-what-3.4.2.tgz

a CSS selector parser

Library home page: https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz

Path to dependency file: typescript-tools/package.json

Path to vulnerable library: typescript-tools/node_modules/css-what/package.json

Dependency Hierarchy:

• license-badger-0.19.0.tgz (Root Library)
  • badge-up-3.0.0.tgz
    • svgo-1.3.2.tgz
      • css-select-2.1.0.tgz
        • ❌ css-what-3.4.2.tgz (Vulnerable Library)

Found in HEAD commit: 94a055e45bd6419b98a3f6c030632bac663aa978

Vulnerability Details

The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.

Publish Date: 2021-05-28

URL: CVE-2021-33587

CVSS 3 Score Details (7.5)

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: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587

Release Date: 2021-05-28

Fix Resolution: css-what - 5.0.1

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #2024

[mend-bolt-for-github]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #2024

[github-actions]

👋 Thanks for reporting!

[github-actions]

Sorry, friend. As far as this ol' bot can tell, your issue does not properly use one of this repo's available issue templates. Please try again, if you like. (And if I'm confused, please let us know. 😬)

(log)

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #2031] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2021-33587 (High) detected in css-what-3.4.2.tgz #2024] CVE-2021-33587 (High) detected in css-what-3.4.2.tgz (100%)
• [CVE-2020-8203 (High) detected in lodash-2.4.2.tgz #2023] CVE-2020-8203 (High) detected in lodash-2.4.2.tgz (78.17%)
• [CVE-2020-7753 (High) detected in trim-0.0.1.tgz #2021] CVE-2020-7753 (High) detected in trim-0.0.1.tgz (75.79%)
• [CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz #2016] CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz (80.12%)
• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)

[github-actions]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[mend-bolt-for-github]

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

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2020-8203 (High) detected in lodash-2.4.2.tgz #1901] CVE-2020-8203 (High) detected in lodash-2.4.2.tgz (78.17%)

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2020-8203 (High) detected in lodash-2.4.2.tgz #1901] CVE-2020-8203 (High) detected in lodash-2.4.2.tgz (78.17%)

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2019-10744 (High) detected in lodash-2.4.2.tgz #2043] CVE-2019-10744 (High) detected in lodash-2.4.2.tgz (76.39%)
• [CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz #2042] CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz (80.12%)
• [CVE-2020-28469 (High) detected in glob-parent-3.1.0.tgz #2040] CVE-2020-28469 (High) detected in glob-parent-3.1.0.tgz (76.19%)
• [CVE-2021-23358 (High) detected in underscore-1.6.0.tgz #2036] CVE-2021-23358 (High) detected in underscore-1.6.0.tgz (80.18%)
• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #2035] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2020-8203 (High) detected in lodash-2.4.2.tgz #1901] CVE-2020-8203 (High) detected in lodash-2.4.2.tgz (78.17%)

[github-actions]

This issue is potentially a duplicate of one of the following issues:

• [CVE-2021-43616 (High) detected in npm-7.24.2.tgz #2046] CVE-2021-43616 (High) detected in npm-7.24.2.tgz (78.97%)
• [CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz #1910] CVE-2021-3803 (High) detected in nth-check-1.0.2.tgz (81.02%)
• [CVE-2020-8203 (High) detected in lodash-2.4.2.tgz #1901] CVE-2020-8203 (High) detected in lodash-2.4.2.tgz (78.17%)