CVE-2024-46970
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains IntelliJ IDEA before 2024.1 hTML injection via the project name was possible
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA HTML injection vulnerability in JetBrains IntelliJ IDEA allowed malicious HTML content to be injected through the project name field. This could lead to cross-site scripting (XSS) attacks if the injected HTML contained JavaScript code, potentially compromising the IDE's interface or executing malicious scripts in the context of the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2024.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check IntelliJ IDEA versionOpen IntelliJ IDEA, go to Help > About (on Windows) or IntelliJ IDEA > About (on macOS). The version number is displayed in the dialog that opens.Affected if The version shown is less than 2024.1.0 (e.g., 2023.x, 2022.x, etc.)
-
Identify active project configurationsLook at the Welcome screen or open a project. The project name is typically visible in the Project tool window (left sidebar) or in the window title bar.Affected if You have any projects configured in IntelliJ IDEA versions prior to 2024.1.0
-
Check for custom project names with special charactersInspect the project directory names on your filesystem. Navigate to your IntelliJ IDEA projects folder (typically ~/IdeaProjects or a custom location) and review the folder names used for projects.Affected if Any project folder name contains HTML-like characters such as <, >, or script tags (e.g., <script>, <img onerror=)
You are affected if IntelliJ IDEA is installed at a version lower than 2024.1.0 and you have configured projects with names that could contain injected HTML content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2024.1.0
Upgrade IntelliJ IDEA to version 2024.1 or later to receive the patch that properly sanitizes project name input.
2024.1.0 or later
- Open IntelliJ IDEA and navigate to Help > Check for Updates (or IntelliJ IDEA > Check for Updates on macOS)
- In the update dialog, if an update to version 2024.1.0 or later is available, click Update
- Alternatively, download the latest version (2024.1.0 or later) from the official JetBrains website at https://www.jetbrains.com/idea/download/
- Restart IntelliJ IDEA after the update completes
- Verify the fix by confirming the project name field now properly sanitizes HTML/script input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data