core-7.4.0.tgz: 1 vulnerabilities (highest severity is: 7.1)

[dev-mend-for-github-com]

Vulnerable Library - core-7.4.0.tgz

Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/package.json

Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_missing_types/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_no_type_update/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_missing_types/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_no_type_update/node_modules/json5/package.json

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (core version)	Remediation Possible**	Reachability
CVE-2022-46175	High	7.1	json5-2.2.1.tgz	Transitive	7.4.3	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2022-46175

Vulnerable Library - json5-2.2.1.tgz

JSON for humans.

Library home page: https://registry.npmjs.org/json5/-/json5-2.2.1.tgz

Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/package.json

Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_missing_types/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_no_type_update/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_missing_types/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_fully_typed/node_modules/json5/package.json,/npm_and_yarn/spec/fixtures/projects/yarn/ts_no_type_update/node_modules/json5/package.json

Dependency Hierarchy:

• core-7.4.0.tgz (Root Library)
  • ❌ json5-2.2.1.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The parse method of the JSON5 library before and including versions 1.0.1 and 2.2.1 does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from JSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. JSON5.parse should restrict parsing of __proto__ keys when parsing JSON strings to objects. As a point of reference, the JSON.parse method included in JavaScript ignores __proto__ keys. Simply changing JSON5.parse to JSON.parse in the examples above mitigates this vulnerability. This vulnerability is patched in json5 versions 1.0.2, 2.2.2, and later.

Publish Date: 2022-12-24

URL: CVE-2022-46175

CVSS 3 Score Details (7.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2022-46175

Release Date: 2022-12-24

Fix Resolution (json5): 2.2.2

Direct dependency fix Resolution (@babel/core): 7.4.3

In order to enable automatic remediation, please create workflow rules

---

In order to enable automatic remediation for this issue, please create workflow rules