CVE-2022-46827
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.3 an XXE attack leading to SSRF via requests to custom plugin repositories 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 · high confidenceThis is an XML External Entity (XXE) vulnerability in IntelliJ IDEA versions prior to 2022.3 that allows attackers to inject malicious XML when the IDE parses responses from custom plugin repositories. The XXE can be leveraged to perform Server-Side Request Forgery (SSRF), enabling the victim's IDE to make arbitrary HTTP requests to internal or external resources controlled by the attacker.
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.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Determine your IntelliJ IDEA versionOpen IntelliJ IDEA and navigate to Help > About (or equivalent menu in your OS) to view the exact version number displayedAffected if The displayed version is any release prior to 2022.3 (for example, 2022.2.x, 2022.1.x, or earlier major versions)
-
Identify configured plugin repositoriesNavigate to Settings > Plugins > Manage Plugin Repositories (or equivalent path in your version) and list all configured repository URLsAffected if Any custom or third-party plugin repository URLs are listed in addition to the default JetBrains repositories
-
Verify trust status of plugin repositoriesReview each repository URL from the previous step and determine its origin and whether it comes from a trusted or internal sourceAffected if Any plugin repository URL originates from an untrusted, public, or attacker-controlled domain
You are affected if your IntelliJ IDEA version is below 2022.3 AND you have custom plugin repositories configured, particularly from untrusted sources.
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.3
Upgrade IntelliJ IDEA to version 2022.3 or later. If using custom plugin repositories, ensure they are from trusted sources and verify repository configurations.
2022.3 or later
- Download IntelliJ IDEA 2022.3 or later from the official JetBrains website (www.jetbrains.com)
- Install the new version, ensuring you back up your settings and plugins
- Restart IntelliJ IDEA after installation
- Verify the vulnerability is resolved by confirming the XXE parser configuration has been updated in the plugin repository handling code
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46827 — 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-46827 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