Quick answers
- Is CVE-2021-23509 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-23509 being exploited in the wild.
- How severe is CVE-2021-23509?
- Low severity, with a CVSS score of 3.1, published 8 November 2021.
- Which products and versions are affected?
- json-ptr (npm) SEMVER:introduced=0,fixed=3.0.0.
- Is there a fix for CVE-2021-23509?
- Yes. json-ptr (npm): upgrade to 3.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2021-23509 attacked?
- It is attacked over the network.
- Am I affected by CVE-2021-23509?
- Check whether you run json-ptr (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- json-ptr (npm): upgrade to 3.0.0 or later
npm install json-ptr@3.0.0
Technical details
The vulnerability is a prototype pollution issue caused by type confusion in json-ptr versions before 3.0.0. When user-provided keys in the pointer parameter are arrays instead of expected string types, the vulnerable code fails to properly validate the input, allowing attackers to bypass the protections added for CVE-2020-7766. This is a network-reachable vulnerability affecting any application that processes untrusted pointer specifications. Successful exploitation enables modification of object prototypes or properties, potentially leading to privilege escalation, data integrity compromise, or information disclosure. The fix was released in version 3.0.0.
Affected products
- flitbit json-ptr before 3.0.0
Identifiers
- CVE-2021-23509
- GHSA-8gwj-8hxc-285w
Timeline
- 2021-11-08: disclosed
- 2021-11-08: patched: Fixed in version 3.0.0