Bug 2156333 (CVE-2022-4742) - CVE-2022-4742 json-pointer: prototype pollution in json-pointer
Summary: CVE-2022-4742 json-pointer: prototype pollution in json-pointer
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-4742
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2156334
TreeView+ depends on / blocked
 
Reported: 2022-12-26 12:51 UTC by Avinash Hanwate
Modified: 2023-06-27 15:42 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-06-27 15:42:37 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:3815 0 None None None 2023-06-27 11:29:02 UTC

Description Avinash Hanwate 2022-12-26 12:51:22 UTC
A vulnerability, which was classified as critical, has been found in json-pointer. Affected by this issue is the function set of the file index.js. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). The attack may be launched remotely. The name of the patch is 859c9984b6c407fc2d5a0a7e47c7274daa681941. It is recommended to apply a patch to fix this issue. VDB-216794 is the identifier assigned to this vulnerability.

https://github.com/manuelstofer/json-pointer/commit/859c9984b6c407fc2d5a0a7e47c7274daa681941
https://github.com/manuelstofer/json-pointer/pull/36
https://vuldb.com/?ctiid.216794
https://vuldb.com/?id.216794

Comment 3 errata-xmlrpc 2023-06-27 11:29:00 UTC
This issue has been addressed in the following products:

  RHINT Service Registry 2.4.3 GA

Via RHSA-2023:3815 https://access.redhat.com/errata/RHSA-2023:3815

Comment 4 Product Security DevOps Team 2023-06-27 15:42:35 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-4742


Note You need to log in before you can comment on or make changes to this bug.