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

@storm-stack/web-docs-1.2.3.tgz: 1 vulnerabilities (highest severity is: 5.3) #86

Open
mend-bolt-for-github bot opened this issue Jun 11, 2024 · 0 comments

Comments

@mend-bolt-for-github
Copy link
Contributor

Vulnerable Library - @storm-stack/web-docs-1.2.3.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Found in HEAD commit: 34f0d07a576eecdbc43254a5cf7714bef5cc5ee9

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (@storm-stack/web-docs version) Remediation Possible**
CVE-2024-37168 Medium 5.3 grpc-js-1.9.13.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-37168

Vulnerable Library - grpc-js-1.9.13.tgz

Library home page: https://registry.npmjs.org/@grpc/grpc-js/-/grpc-js-1.9.13.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

  • @storm-stack/web-docs-1.2.3.tgz (Root Library)
    • otel-0.3.0.tgz
      • exporter-trace-otlp-grpc-0.38.0.tgz
        • grpc-js-1.9.13.tgz (Vulnerable Library)

Found in HEAD commit: 34f0d07a576eecdbc43254a5cf7714bef5cc5ee9

Found in base branch: main

Vulnerability Details

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to versions 1.10.9, 1.9.15, and 1.8.22, there are two separate code paths in which memory can be allocated per message in excess of the grpc.max_receive_message_length channel option: If an incoming message has a size on the wire greater than the configured limit, the entire message is buffered before it is discarded; and/or if an incoming message has a size within the limit on the wire but decompresses to a size greater than the limit, the entire message is decompressed into memory, and on the server is not discarded. This has been patched in versions 1.10.9, 1.9.15, and 1.8.22.

Publish Date: 2024-06-10

URL: CVE-2024-37168

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-7v5v-9h63-cj86

Release Date: 2024-06-10

Fix Resolution: @grpc/grpc-js - 1.8.22,1.9.15,1.10.9

Step up your Open Source Security Game with Mend here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants