HTML injection via unescaped project name
Published Sep 16, 2024 · Updated Sep 16, 2024
HTML injection in JetBrains IntelliJ IDEA before 2024.1 allows attackers to render crafted markup through a malicious project name. The project-name display interprets embedded markup instead of neutralizing it, but JetBrains has not identified the responsible rendering component. Exploitation requires local user interaction with an attacker-controlled project, and the vendor's assessment limits the consequence to information disclosure.
Summary
What happened
HTML injection in JetBrains IntelliJ IDEA before 2024.1 allows attackers to render crafted markup through a malicious project name. The project-name display interprets embedded markup instead of neutralizing it, but JetBrains has not identified the responsible rendering component. Exploitation requires local user interaction with an attacker-controlled project, and the vendor's assessment limits the consequence to information disclosure.
The record
- CVE
- CVE-2024-46970
- Published
- Sep 16, 2024
- Updated
- Sep 16, 2024
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-79
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=0 <2024.1
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