Local code execution via workspace deserialization
Published Feb 3, 2021 · Updated Aug 3, 2024
Insecure deserialization in JetBrains IntelliJ IDEA before 2020.3 allows local users to execute code through workspace-model data. JetBrains identifies the workspace model as the deserialization locus but has not disclosed the affected parser, serialized format, or validation failure. Exploitation requires local low-privileged access and runs code in the security context of the affected IDE process.
Summary
What happened
Insecure deserialization in JetBrains IntelliJ IDEA before 2020.3 allows local users to execute code through workspace-model data. JetBrains identifies the workspace model as the deserialization locus but has not disclosed the affected parser, serialized format, or validation failure. Exploitation requires local low-privileged access and runs code in the security context of the affected IDE process.
The record
- CVE
- CVE-2021-25758
- Published
- Feb 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, CAPEC-586
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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