CVE-2022-29817
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 2022.1 reflected XSS via error messages in internal web server 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 reflected Cross-Site Scripting (XSS) vulnerability exists in the internal web server of JetBrains IntelliJ IDEA versions prior to 2022.1. The vulnerability allows injection of malicious scripts through error messages displayed by the internal web server, potentially enabling session hijacking or credential theft when the IDE is used.
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< 2022.1CVSS 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 installed versionOpen the IDE and go to Help > About (on Windows/Linux) or IntelliJ IDEA > About (on macOS). The version number is displayed in the dialog. Alternatively, check the installation directory for version markers.Affected if The version shown is any release prior to 2022.1 (for example, 2021.3, 2021.2, etc.)
-
Confirm internal web server accessibilityThe internal web server in IntelliJ is typically accessible on localhost ports (commonly 63342, 63343, or other internal ports used by the IDE for features like the embedded server, preview panels, or debugging web applications).Affected if You actively use or have enabled IntelliJ's internal web server features (such as running web applications locally, using the embedded server, or accessing internal preview functionality) while running a version below 2022.1.
You are affected if your installed IntelliJ IDEA version is before 2022.1 AND you use the IDE's internal web server functionality.
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 · scoped2022.1
Upgrade JetBrains IntelliJ IDEA to version 2022.1 or later to receive the security patch. Alternatively, disable the internal web server functionality if not required for development workflows.
IntelliJ IDEA 2022.1 or later
- Back up your IntelliJ IDEA settings and projects
- Download IntelliJ IDEA 2022.1 or later from the official JetBrains website (www.jetbrains.com)
- Install the new version, or use the IDE's built-in update mechanism (Help > Check for Updates)
- Restart IntelliJ IDEA after the update completes
- Verify the update was successful by checking Help > About
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-2022-29817 — 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-2022-29817 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