Code execution via unchecked prototype-path expansion
Published Apr 26, 2021 · Updated Apr 30, 2025
Prototype pollution in safe-obj 1.0.0 through 1.0.2 allows remote attackers to cause denial of service or execute code via a crafted path. The expand function splits the path on dots, follows inherited properties with the in operator, and recursively assigns the supplied value without rejecting proto, constructor, or prototype segments. Exploitation requires a consuming application to pass attacker-controlled path and value data to expand; code execution additionally depends on a usable downstream gadget.
Summary
What happened
Prototype pollution in safe-obj 1.0.0 through 1.0.2 allows remote attackers to cause denial of service or execute code via a crafted path. The expand function splits the path on dots, follows inherited properties with the in operator, and recursively assigns the supplied value without rejecting proto, constructor, or prototype segments. Exploitation requires a consuming application to pass attacker-controlled path and value data to expand; code execution additionally depends on a usable downstream gadget.
The record
- CVE
- CVE-2021-25928
- Published
- Apr 26, 2021
- Updated
- Apr 30, 2025
- Vendor
- Manta Media
- Product
- safe-obj
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2021CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0, 1.0.1, 1.0.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo