temporalio/benchmark-matrix

aws-5.18.0.tgz: 1 vulnerabilities (highest severity is: 5.3) - autoclosed

mend-for-github-com opened this issue · 1 comments

mend-for-github-com commented
Vulnerable Library - aws-5.18.0.tgz

Path to dependency file: /stacks/package.json

Path to vulnerable library: /stacks/node_modules/xml2js/package.json,/environments/aws/node_modules/xml2js/package.json

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (aws version) Remediation Available
CVE-2023-0842 Medium 5.3 xml2js-0.4.19.tgz Transitive 5.19.0 ✅

Details

CVE-2023-0842

Vulnerable Library - xml2js-0.4.19.tgz

Simple XML to JavaScript object converter.

Library home page: https://registry.npmjs.org/xml2js/-/xml2js-0.4.19.tgz

Path to dependency file: /stacks/package.json

Path to vulnerable library: /stacks/node_modules/xml2js/package.json,/environments/aws/node_modules/xml2js/package.json

Dependency Hierarchy:

  • aws-5.18.0.tgz (Root Library)
    • aws-sdk-2.1237.0.tgz
      • ❌ xml2js-0.4.19.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

xml2js version 0.4.23 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the proto property to be edited.

Publish Date: 2023-04-05

URL: CVE-2023-0842

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.

Suggested Fix

Type: Upgrade version

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

Release Date: 2023-04-05

Fix Resolution (xml2js): 0.5.0

Direct dependency fix Resolution (@pulumi/aws): 5.19.0

⛑️ Automatic Remediation is available for this issue

⛑️ Automatic Remediation is available for this issue.

mend-for-github-com commented

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