Path to vulnerable library: /admin/node_modules/babel-register/node_modules/json5/package.json,/client/node_modules/react-dev-utils/node_modules/json5/package.json,/client/node_modules/jest-config/node_modules/json5/package.json,/client/node_modules/jest-runtime/node_modules/json5/package.json,/admin/node_modules/react-dev-utils/node_modules/json5/package.json,/admin/node_modules/jest-runtime/node_modules/json5/package.json,/client/node_modules/babel-register/node_modules/json5/package.json,/admin/node_modules/jest-config/node_modules/json5/package.json
Path to vulnerable library: /admin/node_modules/loader-utils/node_modules/json5/package.json,/client/node_modules/loader-utils/node_modules/json5/package.json
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.
CVE-2022-46175 - High Severity Vulnerability
json5-0.5.1.tgz
JSON for the ES5 era.
Library home page: https://registry.npmjs.org/json5/-/json5-0.5.1.tgz
Path to dependency file: /admin/package.json
Path to vulnerable library: /admin/node_modules/babel-register/node_modules/json5/package.json,/client/node_modules/react-dev-utils/node_modules/json5/package.json,/client/node_modules/jest-config/node_modules/json5/package.json,/client/node_modules/jest-runtime/node_modules/json5/package.json,/admin/node_modules/react-dev-utils/node_modules/json5/package.json,/admin/node_modules/jest-runtime/node_modules/json5/package.json,/client/node_modules/babel-register/node_modules/json5/package.json,/admin/node_modules/jest-config/node_modules/json5/package.json
Dependency Hierarchy: - react-scripts-2.1.3.tgz (Root Library) - jest-23.6.0.tgz - jest-cli-23.6.0.tgz - jest-runtime-23.6.0.tgz - babel-core-6.26.3.tgz - :x: **json5-0.5.1.tgz** (Vulnerable Library)
json5-1.0.1.tgz
JSON for humans.
Library home page: https://registry.npmjs.org/json5/-/json5-1.0.1.tgz
Path to dependency file: /admin/package.json
Path to vulnerable library: /admin/node_modules/loader-utils/node_modules/json5/package.json,/client/node_modules/loader-utils/node_modules/json5/package.json
Dependency Hierarchy: - react-scripts-2.1.3.tgz (Root Library) - webpack-2.4.1.tgz - loader-utils-1.2.3.tgz - :x: **json5-1.0.1.tgz** (Vulnerable Library)
json5-2.1.0.tgz
JSON for humans.
Library home page: https://registry.npmjs.org/json5/-/json5-2.1.0.tgz
Path to dependency file: /client/package.json
Path to vulnerable library: /client/node_modules/json5/package.json,/admin/node_modules/json5/package.json
Dependency Hierarchy: - react-scripts-2.1.3.tgz (Root Library) - core-7.1.6.tgz - :x: **json5-2.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 5ce352c75fbe6372f4f2df4d5ed63e7ced820f77
Found in base branch: master
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
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.Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-46175
Release Date: 2022-12-24
Fix Resolution (json5): 1.0.2
Direct dependency fix Resolution (react-scripts): 3.0.0
Fix Resolution (json5): 1.0.2
Direct dependency fix Resolution (react-scripts): 3.0.0
Fix Resolution (json5): 1.0.2
Direct dependency fix Resolution (react-scripts): 3.0.0
Step up your Open Source Security Game with Mend here