Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting 389-ds-base-snmp package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-389DSBASESNMP-3183160
- published 26 Dec 2022
- disclosed 24 Dec 2022
Introduced: 24 Dec 2022
CVE-2022-46175 Open this link in a new tabHow to fix?
There is no fixed version for Centos:8 389-ds-base-snmp.
NVD Description
Note: Versions mentioned in the description apply only to the upstream 389-ds-base-snmp package and not the 389-ds-base-snmp package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
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.
References
- https://access.redhat.com/security/cve/CVE-2022-46175
- https://github.com/json5/json5/security/advisories/GHSA-9c47-m6qq-7p4h
- https://github.com/json5/json5/issues/199
- https://github.com/json5/json5/issues/295
- https://github.com/json5/json5/pull/298
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3S26TLPLVFAJTUN3VIXFDEBEXDYO22CE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3S26TLPLVFAJTUN3VIXFDEBEXDYO22CE/
- https://lists.debian.org/debian-lts-announce/2023/11/msg00021.html