Application disruption via prototype-path deletion
Published Jan 19, 2021 · Updated Sep 17, 2024
Denial of service in JointJS before 3.3.0 allows remote attackers to disrupt a consuming application through a crafted property path. The unsetByPath utility follows proto or constructor/prototype path segments and deletes inherited properties instead of limiting deletion to the supplied object. Exploitation requires a consuming application to pass attacker-controlled paths; deleting Object.prototype.toString causes a TypeError and interrupts affected application logic.
Summary
What happened
Denial of service in JointJS before 3.3.0 allows remote attackers to disrupt a consuming application through a crafted property path. The unsetByPath utility follows proto or constructor/prototype path segments and deletes inherited properties instead of limiting deletion to the supplied object. Exploitation requires a consuming application to pass attacker-controlled paths; deleting Object.prototype.toString causes a TypeError and interrupts affected application logic.
The record
- CVE
- CVE-2020-28479
- Published
- Jan 19, 2021
- Updated
- Sep 17, 2024
- Vendor
- client IO
- Product
- JointJS
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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=unspecified <3.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- unsetByPath prototype-deletion proof of conceptproof of concept · demonstrated
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