Unauthenticated file read via XSLT debugger misconfiguration
Published Jan 31, 2020 · Updated Aug 4, 2024
Arbitrary file read in the XSLT debugger plugin in JetBrains IntelliJ IDEA 2019.2 allows remote attackers to read local files over a network. JetBrains identifies a plugin misconfiguration but has not published the affected setting, request handler, or file-path processing error. No authentication or user interaction is required, and successful exploitation exposes files readable by the running IDE process without altering them.
Summary
What happened
Arbitrary file read in the XSLT debugger plugin in JetBrains IntelliJ IDEA 2019.2 allows remote attackers to read local files over a network. JetBrains identifies a plugin misconfiguration but has not published the affected setting, request handler, or file-path processing error. No authentication or user interaction is required, and successful exploitation exposes files readable by the running IDE process without altering them.
The record
- CVE
- CVE-2020-7914
- Published
- Jan 31, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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