Quick answers
- Is CVE-2023-26121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-26121 being exploited in the wild.
- How severe is CVE-2023-26121?
- Low severity, with a CVSS score of 3.1, published 11 April 2023.
- Which products and versions are affected?
- safe-eval (npm) SEMVER:introduced=0,last_affected=0.4.2.
- Is there a fix for CVE-2023-26121?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-26121 attacked?
- It is attacked over the network.
- Am I affected by CVE-2023-26121?
- Check whether you run safe-eval (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.
Technical details
The vulnerability is a prototype pollution flaw (CWE-1321) in the safeEval function caused by improper sanitization of input parameters. An attacker can craft malicious code that escapes the sandbox and pollutes the prototype chain of JavaScript objects, affecting all objects created thereafter. The attack is network-exploitable with no authentication or user interaction required, and impacts confidentiality, integrity, and availability. All versions up to 0.4.2 are affected; no patch information is currently available.
Affected products
- safe-eval safe-eval 0.4.2 and all previous versions
Identifiers
- CVE-2023-26121
- GHSA-hcg3-56jf-x4vh
Timeline
- 2023-04-11: disclosed
- 2023-01-02: other: Vulnerability initially reported on GitHub