Skip to content

kleros-v2-contracts-0.11.0.tgz: 5 vulnerabilities (highest severity is: 7.5) - autoclosed #2062

@mend-bolt-for-github

Description

@mend-bolt-for-github
Vulnerable Library - kleros-v2-contracts-0.11.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Vulnerabilities

Vulnerability Severity CVSS Dependency Type Fixed in (kleros-v2-contracts version) Remediation Possible**
CVE-2024-37890 High 7.5 ws-7.4.6.tgz Transitive N/A*
CVE-2024-21538 High 7.5 cross-spawn-6.0.5.tgz Transitive N/A*
CVE-2025-27789 Medium 6.2 runtime-7.26.0.tgz Transitive N/A*
CVE-2025-53638 Medium 5.3 solady-0.0.182.tgz Transitive N/A*
CVE-2022-25883 Medium 5.3 semver-5.7.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-2024-37890

Vulnerable Library - ws-7.4.6.tgz

Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js

Library home page: https://registry.npmjs.org/ws/-/ws-7.4.6.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • kleros-v2-contracts-0.11.0.tgz (Root Library)
    • contracts-1.4.0.tgz
      • contracts-0.6.0.tgz
        • core-utils-0.12.0.tgz
          • providers-5.7.2.tgz
            • ws-7.4.6.tgz (Vulnerable Library)

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Found in base branch: dev

Vulnerability Details

ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.

Publish Date: 2024-06-17

URL: CVE-2024-37890

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: GHSA-3h5v-q93c-6h6q

Release Date: 2024-06-17

Fix Resolution: ws - 5.2.4,6.2.3,7.5.10,8.17.1

Step up your Open Source Security Game with Mend here

CVE-2024-21538

Vulnerable Library - cross-spawn-6.0.5.tgz

Cross platform child_process#spawn and child_process#spawnSync

Library home page: https://registry.npmjs.org/cross-spawn/-/cross-spawn-6.0.5.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • kleros-v2-contracts-0.11.0.tgz (Root Library)
    • contracts-1.4.0.tgz
      • nitro-contracts-3.0.0.tgz
        • patch-package-6.5.1.tgz
          • cross-spawn-6.0.5.tgz (Vulnerable Library)

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Found in base branch: dev

Vulnerability Details

Versions of the package cross-spawn before 6.0.6, from 7.0.0 and before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.

Publish Date: 2024-11-08

URL: CVE-2024-21538

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://nvd.nist.gov/vuln/detail/CVE-2024-21538

Release Date: 2024-11-08

Fix Resolution: https://github.com/moxystudio/node-cross-spawn.git - v7.0.5

Step up your Open Source Security Game with Mend here

CVE-2025-27789

Vulnerable Library - runtime-7.26.0.tgz

babel's modular runtime helpers

Library home page: https://registry.npmjs.org/@babel/runtime/-/runtime-7.26.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • kleros-v2-contracts-0.11.0.tgz (Root Library)
    • contracts-1.4.0.tgz
      • cli-2.28.1.tgz
        • get-packages-1.1.3.tgz
          • runtime-7.26.0.tgz (Vulnerable Library)

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Found in base branch: dev

Vulnerability Details

Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 to compile regular expression named capturing groups, Babel will generate a polyfill for the ".replace" method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to ".replace"). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the ".replace" method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of ".replace". This problem has been fixed in "@babel/helpers" and "@babel/runtime" 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on "@babel/helpers", and instead depend on "@babel/core" (which itself depends on "@babel/helpers"). Upgrading to "@babel/core" 7.26.10 is not required, but it guarantees use of a new enough "@babel/helpers" version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.

Publish Date: 2025-03-11

URL: CVE-2025-27789

CVSS 3 Score Details (6.2)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Local
    • 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: GHSA-968p-4wvh-cqc8

Release Date: 2025-03-11

Fix Resolution: @babel/runtime-corejs2 - 7.26.10

Step up your Open Source Security Game with Mend here

CVE-2025-53638

Vulnerable Library - solady-0.0.182.tgz

Library home page: https://registry.npmjs.org/solady/-/solady-0.0.182.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • kleros-v2-contracts-0.11.0.tgz (Root Library)
    • contracts-1.4.0.tgz
      • nitro-contracts-3.0.0.tgz
        • solady-0.0.182.tgz (Vulnerable Library)

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Found in base branch: dev

Vulnerability Details

Solady is software that provides Solidity snippets with APIs. Starting in version 0.0.125 and prior to version 0.1.24, when an account is deployed via a proxy, using regular Solidity to call its initialization function may result in a silent failure, if the initialization function does not return a "bool" or some other return data. This is because regular Solidity uses "extcodesize(proxy)" to decide if call succeeds. This is insufficient in the case when the proxy points to an empty implementation. Users should upgrade to Solady v0.1.24 or later to receive a patch. Deploy any affected implementations and their factories on new EVM chains as soon as possible.

Publish Date: 2025-07-17

URL: CVE-2025-53638

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: Low
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Step up your Open Source Security Game with Mend here

CVE-2022-25883

Vulnerable Library - semver-5.7.1.tgz

The semantic version parser used by npm.

Library home page: https://registry.npmjs.org/semver/-/semver-5.7.1.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • kleros-v2-contracts-0.11.0.tgz (Root Library)
    • contracts-1.4.0.tgz
      • nitro-contracts-3.0.0.tgz
        • patch-package-6.5.1.tgz
          • cross-spawn-6.0.5.tgz
            • semver-5.7.1.tgz (Vulnerable Library)

Found in HEAD commit: a3f5416a71e1112e0fb8a2d29dc240c8665c7335

Found in base branch: dev

Vulnerability Details

Versions of the package semver before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2023-06-21

URL: CVE-2022-25883

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

Origin: GHSA-c2qf-rxjj-qqgw

Release Date: 2023-06-21

Fix Resolution: semver - 5.7.2,6.3.1,7.5.2;org.webjars.npm:semver:7.5.2

Step up your Open Source Security Game with Mend here

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions