Most recent entries from all

bdu:2023-07864

certfr-2023-avi-0428 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre…

certfr-2023-avi-0428

EUVD-2026-19692

fkie_cve-2022-46175

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.

GHSA-9c47-m6qq-7p4h — Prototype Pollution in JSON5 via Parse Method

Affected: npm: json5

The `parse` method of the JSON5 library before and including version `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.

## Impact 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.

## Mitigation This vulnerability is patched in json5 v2.2.2 and later. A patch has also been backported for json5 v1 in versions v1.0.2 and later.

## Details Suppose a developer wants to allow users and admins to perform some risky operation, but they want to restrict what non-admins can do. To accomplish this, they accept a JSON blob from the user, parse it using `JSON5.parse`, confirm that the provided data does not set some sensitive keys, and then performs the risky operation using the validated data: ```js const JSON5 = require('json5');

const…

gsd-2022-46175

msrc_CVE-2022-46175 — JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for co…

msrc_CVE-2022-46175

RHSA-2023:0634 — Red Hat Security Advisory: Red Hat OpenShift (Logging Subsystem) security update

glob-parent: Regular Expression Denial of Service json5: Prototype Pollution in JSON5 via Parse Method

UBUNTU-CVE-2022-46175

Affected: Ubuntu:Pro:18.04:LTS: node-json5, Ubuntu:20.04:LTS: node-json5, Ubuntu:Pro:22.04:LTS: node-json5

WID-SEC-W-2023-0328 — Red Hat OpenShift: Mehrere Schwachstellen

Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial of Service Angriff durchzuführen oder Daten zu manipulieren.