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 pars…
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2022-46175
PublishedJSON5 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.
- Source published
- 24 Dec 2022 00:00:00 UTC
- Source modified
- 3 Aug 2024 14:24:03 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H
euvd · EUVD-2022-7580
PublishedJSON5 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Dec 24, 2022, 12:00:00 AM
dateUpdated: Aug 3, 2024, 2:24:03 PM
20 related source bulletins · separate from aliases
RHSA-2023:3742: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.13.0 security and bug fix update
CVE-2020-16250 · CVE-2020-16251 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-4235 · CVE-2021-4238 · CVE-2021-43998 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-3517 · CVE-2022-21824 · CVE-2022-23540 · CVE-2022-23541 · CVE-2022-27664 · CVE-2022-30635 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-38149 · CVE-2022-38900 · CVE-2022-41316 · CVE-2022-41715 · CVE-2022-41717 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-46175 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-24999 · CVE-2023-25000
RHSA-2023:1047: Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 for OpenShift image security and enhancement update
CVE-2018-14040 · CVE-2018-14042 · CVE-2019-11358 · CVE-2020-11022 · CVE-2021-35065 · CVE-2021-44906 · CVE-2022-1274 · CVE-2022-1438 · CVE-2022-1471 · CVE-2022-2764 · CVE-2022-3782 · CVE-2022-3916 · CVE-2022-4039 · CVE-2022-24785 · CVE-2022-25857 · CVE-2022-31129 · CVE-2022-37603 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-45047 · CVE-2022-45693 · CVE-2022-46175 · CVE-2022-46363 · CVE-2022-46364 · CVE-2023-0091 · CVE-2023-0264
WID-SEC-W-2023-1350: Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern
CVE-2017-16042 · CVE-2018-25032 · CVE-2019-10744 · CVE-2019-10746 · CVE-2019-20149 · CVE-2020-13822 · CVE-2020-15138 · CVE-2020-28469 · CVE-2020-7662 · CVE-2020-7753 · CVE-2020-7774 · CVE-2020-8116 · CVE-2020-8169 · CVE-2020-8177 · CVE-2020-8203 · CVE-2020-8231 · CVE-2020-8284 · CVE-2020-8285 · CVE-2020-8286 · CVE-2021-20095 · CVE-2021-22876 · CVE-2021-22890 · CVE-2021-22897 · CVE-2021-22898 · CVE-2021-22901 · CVE-2021-22922 · CVE-2021-22923 · CVE-2021-22924 · CVE-2021-22925 · CVE-2021-22926 · CVE-2021-22945 · CVE-2021-22946 · CVE-2021-22947 · CVE-2021-23343 · CVE-2021-23368 · CVE-2021-23382 · CVE-2021-27292 · CVE-2021-29060 · CVE-2021-31566 · CVE-2021-33502 · CVE-2021-33503 · CVE-2021-33587 · CVE-2021-3520 · CVE-2021-36976 · CVE-2021-3803 · CVE-2021-43565 · CVE-2022-1705 · CVE-2022-1962 · CVE-2022-22576 · CVE-2022-23491 · CVE-2022-23772 · CVE-2022-23773 · CVE-2022-23806 · CVE-2022-24675 · CVE-2022-24921 · CVE-2022-24999 · CVE-2022-25858 · CVE-2022-27191 · CVE-2022-27664 · CVE-2022-27774 · CVE-2022-27775 · CVE-2022-27776 · CVE-2022-27778 · CVE-2022-27779 · CVE-2022-27780 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-28131 · CVE-2022-28327 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-29526 · CVE-2022-29804 · CVE-2022-30115 · CVE-2022-30580 · CVE-2022-30629 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-30634 · CVE-2022-30635 · CVE-2022-31129 · CVE-2022-32148 · CVE-2022-32189 · CVE-2022-32205 · CVE-2022-32206 · CVE-2022-32207 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-33987 · CVE-2022-3517 · CVE-2022-35252 · CVE-2022-35260 · CVE-2022-35737 · CVE-2022-36227 · CVE-2022-37434 · CVE-2022-37599 · CVE-2022-37601 · CVE-2022-37603 · CVE-2022-37616 · CVE-2022-38900 · CVE-2022-40023 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-41715 · CVE-2022-41716 · CVE-2022-41720 · CVE-2022-4200 · CVE-2022-42004 · CVE-2022-42915 · CVE-2022-42916 · CVE-2022-4304 · CVE-2022-43551 · CVE-2022-43552 · CVE-2022-43680 · CVE-2022-46175 · CVE-2023-0215 · CVE-2023-0286 · CVE-2023-1370 · CVE-2023-23914 · CVE-2023-23915 · CVE-2023-23916 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538
WID-SEC-W-2026-3376: Atlassian Bamboo, Bitbucket, Confluence, Fisheye/Crucible, Jira Software und Jira Service Management: Mehrere Schwachstellen
CVE-2022-46175 · CVE-2026-12143 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-42583 · CVE-2026-44249 · CVE-2026-44728 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-45674 · CVE-2026-47691 · CVE-2026-47759 · CVE-2026-47761 · CVE-2026-47762 · CVE-2026-4800 · CVE-2026-48043 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53404 · CVE-2026-53434 · CVE-2026-54428 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55153 · CVE-2026-55276 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59650 · CVE-2026-59869 · CVE-2026-59879 · CVE-2026-59880 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67320 · CVE-2026-68763 · CVE-2026-69152 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73507 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-75140 · CVE-2026-75595 · CVE-2026-75899 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-8763
RHSA-2024:4631: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.15.0 release
CVE-2022-3064 · CVE-2022-21698 · CVE-2022-28948 · CVE-2022-46175 · CVE-2023-6378 · CVE-2023-39325 · CVE-2023-41080 · CVE-2023-44487 · CVE-2023-45288 · CVE-2023-45648
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 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
CVE-2022-46175
WID-SEC-W-2024-0528: Dell Data Protection Advisor: Mehrere Schwachstellen
CVE-2023-45648 · CVE-2023-42795 · CVE-2023-41080 · CVE-2023-34055 · CVE-2023-28708 · CVE-2023-28154 · CVE-2023-22081 · CVE-2023-22067 · CVE-2023-22025 · CVE-2023-20883 · CVE-2023-20873 · CVE-2023-20863 · CVE-2023-20861 · CVE-2022-46175 · CVE-2022-41854 · CVE-2022-38752 · CVE-2022-38751 · CVE-2022-38750 · CVE-2022-38749 · CVE-2022-37603 · CVE-2022-37601 · CVE-2022-37599 · CVE-2022-31129 · CVE-2022-27772 · CVE-2022-25881 · CVE-2022-25858 · CVE-2022-22971 · CVE-2022-22970 · CVE-2022-22968 · CVE-2022-22965 · CVE-2022-22950 · CVE-2021-43980 · CVE-2021-33037 · CVE-2021-30640 · CVE-2020-5421 · CVE-2020-1938 · CVE-2020-1935 · CVE-2020-13943 · CVE-2020-13935 · CVE-2020-13934 · CVE-2020-11996 · CVE-2019-2684 · CVE-2019-17563 · CVE-2019-12418 · CVE-2019-10072 · CVE-2019-0232 · CVE-2019-0221 · CVE-2019-0199 · CVE-2018-8037 · CVE-2018-8034 · CVE-2018-8014 · CVE-2018-15756 · CVE-2018-1336 · CVE-2018-1305 · CVE-2018-1304 · CVE-2018-1275 · CVE-2018-1272 · CVE-2018-1271 · CVE-2018-1270 · CVE-2018-1257 · CVE-2018-1199 · CVE-2018-1196 · CVE-2018-11784 · CVE-2018-11040 · CVE-2018-11039 · CVE-2017-8046 · CVE-2017-7675 · CVE-2017-7674 · CVE-2017-5664 · CVE-2017-5651 · CVE-2017-5650 · CVE-2017-5648 · CVE-2017-5647 · CVE-2017-18640 · CVE-2017-12617 · CVE-2016-9878 · CVE-2016-8745 · CVE-2016-8735 · CVE-2016-6817 · CVE-2016-6816
RHSA-2023:0634: Red Hat Security Advisory: Red Hat OpenShift (Logging Subsystem) security update
CVE-2021-35065 · CVE-2022-46175
WID-SEC-W-2024-3678: Atlassian Confluence: Mehrere Schwachstellen
CVE-2022-3517 · CVE-2022-46175 · CVE-2023-45859 · CVE-2024-25710
WID-SEC-W-2024-0049: Splunk Enterprise: Mehrere Schwachstellen
CVE-2015-5237 · CVE-2021-23446 · CVE-2022-25883 · CVE-2022-3171 · CVE-2022-3509 · CVE-2022-3510 · CVE-2022-37599 · CVE-2022-37601 · CVE-2022-37603 · CVE-2022-46175 · CVE-2023-2976 · CVE-2023-32695 · CVE-2023-45133 · CVE-2024-22164 · CVE-2024-22165
WID-SEC-W-2023-2229: Splunk Splunk Enterprise: Mehrere Schwachstellen
CVE-2013-7489 · CVE-2018-10237 · CVE-2018-20225 · CVE-2019-20454 · CVE-2019-20838 · CVE-2020-14155 · CVE-2020-28469 · CVE-2020-28851 · CVE-2020-29652 · CVE-2020-8169 · CVE-2020-8177 · CVE-2020-8231 · CVE-2020-8284 · CVE-2020-8285 · CVE-2020-8286 · CVE-2020-8908 · CVE-2021-20066 · CVE-2021-22569 · CVE-2021-22876 · CVE-2021-22890 · CVE-2021-22897 · CVE-2021-22898 · CVE-2021-22901 · CVE-2021-22922 · CVE-2021-22923 · CVE-2021-22924 · CVE-2021-22925 · CVE-2021-22926 · CVE-2021-22945 · CVE-2021-22946 · CVE-2021-22947 · CVE-2021-23343 · CVE-2021-23382 · CVE-2021-27918 · CVE-2021-27919 · CVE-2021-29060 · CVE-2021-29425 · CVE-2021-29923 · CVE-2021-31525 · CVE-2021-31566 · CVE-2021-33194 · CVE-2021-33195 · CVE-2021-33196 · CVE-2021-33197 · CVE-2021-33198 · CVE-2021-34558 · CVE-2021-3520 · CVE-2021-3572 · CVE-2021-36221 · CVE-2021-36976 · CVE-2021-3803 · CVE-2021-38297 · CVE-2021-38561 · CVE-2021-39293 · CVE-2021-41182 · CVE-2021-41183 · CVE-2021-41184 · CVE-2021-41771 · CVE-2021-41772 · CVE-2021-43565 · CVE-2021-44716 · CVE-2021-44717 · CVE-2022-1705 · CVE-2022-1941 · CVE-2022-1962 · CVE-2022-22576 · CVE-2022-2309 · CVE-2022-23491 · CVE-2022-23772 · CVE-2022-23773 · CVE-2022-23806 · CVE-2022-24675 · CVE-2022-24921 · CVE-2022-24999 · CVE-2022-25881 · CVE-2022-27191 · CVE-2022-27536 · CVE-2022-27664 · CVE-2022-27774 · CVE-2022-27775 · CVE-2022-27776 · CVE-2022-27778 · CVE-2022-27779 · CVE-2022-27780 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-28131 · CVE-2022-28327 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-29526 · CVE-2022-29804 · CVE-2022-30115 · CVE-2022-30580 · CVE-2022-30629 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-30634 · CVE-2022-30635 · CVE-2022-31129 · CVE-2022-3171 · CVE-2022-32148 · CVE-2022-32149 · CVE-2022-32189 · CVE-2022-32205 · CVE-2022-32206 · CVE-2022-32207 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-33987 · CVE-2022-3509 · CVE-2022-3510 · CVE-2022-3517 · CVE-2022-35252 · CVE-2022-35260 · CVE-2022-35737 · CVE-2022-36227 · CVE-2022-37599 · CVE-2022-37601 · CVE-2022-37603 · CVE-2022-38900 · CVE-2022-40023 · CVE-2022-40897 · CVE-2022-40899 · CVE-2022-41715 · CVE-2022-41716 · CVE-2022-41720 · CVE-2022-41722 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-42915 · CVE-2022-42916 · CVE-2022-43551 · CVE-2022-43552 · CVE-2022-46175 · CVE-2023-23914 · CVE-2023-23915 · CVE-2023-23916 · CVE-2023-24539 · CVE-2023-24540 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27537 · CVE-2023-27538 · CVE-2023-29400 · CVE-2023-29402 · CVE-2023-29403 · CVE-2023-29404 · CVE-2023-29405 · CVE-2023-40592 · CVE-2023-40593 · CVE-2023-40594 · CVE-2023-40595 · CVE-2023-40596 · CVE-2023-40597 · CVE-2023-40598
WID-SEC-W-2023-0328: Red Hat OpenShift: Mehrere Schwachstellen
CVE-2021-35065 · CVE-2022-46175
RHSA-2025:19094: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.24.0 Release.
CVE-2021-35065 · CVE-2022-3517 · CVE-2022-25883 · CVE-2022-46175 · CVE-2025-9566 · CVE-2025-41248 · CVE-2025-41249 · CVE-2025-55163 · CVE-2025-59343
RHSA-2023:1045: Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 security update on RHEL 9
CVE-2018-14040 · CVE-2018-14042 · CVE-2019-11358 · CVE-2020-11022 · CVE-2020-11023 · CVE-2021-35065 · CVE-2021-44906 · CVE-2022-1274 · CVE-2022-1438 · CVE-2022-1471 · CVE-2022-2764 · CVE-2022-3916 · CVE-2022-4137 · CVE-2022-24785 · CVE-2022-25857 · CVE-2022-31129 · CVE-2022-37603 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-45047 · CVE-2022-45693 · CVE-2022-46175 · CVE-2022-46363 · CVE-2022-46364 · CVE-2023-0091 · CVE-2023-0264
RHSA-2023:1044: Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 security update on RHEL 8
CVE-2018-14040 · CVE-2018-14042 · CVE-2019-11358 · CVE-2020-11022 · CVE-2020-11023 · CVE-2021-35065 · CVE-2021-44906 · CVE-2022-1274 · CVE-2022-1438 · CVE-2022-1471 · CVE-2022-2764 · CVE-2022-3916 · CVE-2022-4137 · CVE-2022-24785 · CVE-2022-25857 · CVE-2022-31129 · CVE-2022-37603 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-45047 · CVE-2022-45693 · CVE-2022-46175 · CVE-2022-46363 · CVE-2022-46364 · CVE-2023-0091 · CVE-2023-0264
RHSA-2023:1049: Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 security update
CVE-2018-14040 · CVE-2018-14042 · CVE-2019-11358 · CVE-2020-11022 · CVE-2020-11023 · CVE-2021-35065 · CVE-2021-44906 · CVE-2022-1274 · CVE-2022-1438 · CVE-2022-1471 · CVE-2022-2237 · CVE-2022-2764 · CVE-2022-3782 · CVE-2022-3916 · CVE-2022-4137 · CVE-2022-24785 · CVE-2022-25857 · CVE-2022-31129 · CVE-2022-37603 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-45047 · CVE-2022-45693 · CVE-2022-46175 · CVE-2022-46363 · CVE-2022-46364 · CVE-2023-0091 · CVE-2023-0264
WID-SEC-W-2023-1542: Red Hat OpenShift: Mehrere Schwachstellen
CVE-2015-20107 · CVE-2018-25032 · CVE-2020-10735 · CVE-2020-16250 · CVE-2020-16251 · CVE-2020-17049 · CVE-2021-28861 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-4231 · CVE-2021-4235 · CVE-2021-4238 · CVE-2021-43519 · CVE-2021-43998 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2021-44964 · CVE-2021-46828 · CVE-2021-46848 · CVE-2022-0670 · CVE-2022-1271 · CVE-2022-1304 · CVE-2022-1348 · CVE-2022-1586 · CVE-2022-1587 · CVE-2022-21824 · CVE-2022-2309 · CVE-2022-23540 · CVE-2022-23541 · CVE-2022-24903 · CVE-2022-2509 · CVE-2022-26280 · CVE-2022-27664 · CVE-2022-2795 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-28805 · CVE-2022-29154 · CVE-2022-30635 · CVE-2022-3094 · CVE-2022-31129 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-33099 · CVE-2022-3358 · CVE-2022-34903 · CVE-2022-3515 · CVE-2022-3517 · CVE-2022-35737 · CVE-2022-36227 · CVE-2022-3715 · CVE-2022-3736 · CVE-2022-37434 · CVE-2022-38149 · CVE-2022-3821 · CVE-2022-38900 · CVE-2022-3924 · CVE-2022-40023 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40897 · CVE-2022-41316 · CVE-2022-41715 · CVE-2022-41717 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-42898 · CVE-2022-42919 · CVE-2022-43680 · CVE-2022-4415 · CVE-2022-45061 · CVE-2022-45873 · CVE-2022-46175 · CVE-2022-47024 · CVE-2022-47629 · CVE-2022-48303 · CVE-2022-48337 · CVE-2022-48338 · CVE-2022-48339 · CVE-2023-0361 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-22809 · CVE-2023-24329 · CVE-2023-2491 · CVE-2023-24999 · CVE-2023-25000 · CVE-2023-25136
RHSA-2023:1043: Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 security update on RHEL 7
CVE-2018-14040 · CVE-2018-14042 · CVE-2019-11358 · CVE-2020-11022 · CVE-2020-11023 · CVE-2021-35065 · CVE-2021-44906 · CVE-2022-1274 · CVE-2022-1438 · CVE-2022-1471 · CVE-2022-2764 · CVE-2022-3916 · CVE-2022-4137 · CVE-2022-24785 · CVE-2022-25857 · CVE-2022-31129 · CVE-2022-37603 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-45047 · CVE-2022-45693 · CVE-2022-46175 · CVE-2022-46363 · CVE-2022-46364 · CVE-2023-0091 · CVE-2023-0264
RHSA-2023:1428: Red Hat Security Advisory: Migration Toolkit for Containers (MTC) 1.7.8 security and bug fix update
CVE-2020-36567 · CVE-2022-24999 · CVE-2022-25881 · CVE-2022-25927 · CVE-2022-37603 · CVE-2022-38900 · CVE-2022-46175 · CVE-2022-48285
RHSA-2023:0934: Red Hat Security Advisory: Migration Toolkit for Applications security and bug fix update
CVE-2020-36567 · CVE-2021-35065 · CVE-2022-24999 · CVE-2022-37601 · CVE-2022-37603 · CVE-2022-41717 · CVE-2022-42920 · CVE-2022-46175
- Source published
- Dec 24, 2022, 12:00:00 AM (timezone not stated)
- Source modified
- Aug 3, 2024, 2:24:03 PM (timezone not stated)
- Saved here
- 18 Nov 2026 03:34:16 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H
nvd · CVE-2022-46175
PublishedJSON5 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-1321
Original publisher date fields
published: 2022-12-24T04:15:08.787
lastModified: 2026-06-17T05:11:21.953
2 source CPE criteria · context only
- cpe:2.3:a:json5:json5:*:*:*:*:*:node.js:*:*
- cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 24 Dec 2022 04:15:08 UTC
- Source modified
- 17 Jun 2026 05:11:21 UTC
- Saved here
- 24 Oct 2026 21:17:16 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H
CVSS 3.1 · [email protected] · Primary · 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv · GHSA-9c47-m6qq-7p4h
PublishedThe `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 doSomethingDangerous = (props) => { if (props.isAdmin) { console.log('Doing dangerous thing as admin.'); } else { console.log('Doing dangerous thing as user.'); } }; const secCheckKeysSet = (obj, searchKeys) => { let searchKeyFound = false; Object.keys(obj).forEach((key) => { if (searchKeys.indexOf(key) > -1) { searchKeyFound = true; } }); return searchKeyFound; }; const props = JSON5.parse('{"foo": "bar"}'); if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) { doSomethingDangerous(props); // "Doing dangerous thing as user." } else { throw new Error('Forbidden...'); } ``` If the user attempts to set the `isAdmin` key, their request will be rejected: ```js const props = JSON5.parse('{"foo": "bar", "isAdmin": true}'); if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) { doSomethingDangerous(props); } else { throw new Error('Forbidden...'); // Error: Forbidden... } ``` However, users can instead set the `__proto__` key to `{"isAdmin": true}`. `JSON5` will parse this key and will set the `isAdmin` key on the prototype of the returned object, allowing the user to bypass the security check and run their request as an admin: ```js const props = JSON5.parse('{"foo": "bar", "__proto__": {"isAdmin": true}}'); if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) { doSomethingDangerous(props); // "Doing dangerous thing as admin." } else { throw new Error('Forbidden...'); } ```
- Source published
- 29 Dec 2022 01:51:03 UTC
- Source modified
- 10 Sep 2026 03:49:56 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H
Publisher rating · HIGH