CVE-2022-48431
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 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation.
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 confidenceIn JetBrains IntelliJ IDEA before version 2023.1, the 'Trust Project' security confirmation dialog could be bypassed during project import for certain Gradle and Maven projects, allowing potentially malicious project code to be loaded without user warning.
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< 2023.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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, or check the installation directory (typically IDE60Xuild.txt or similar version file in the installation folder)Affected if The reported version is any version below 2023.1 (for example, 2022.3, 2022.2, 2022.1, 2021.x, etc.)
-
Identify installation sourceDetermine if IntelliJ was installed via JetBrains Toolbox, direct download, or a system package manager - different locations may have different version filesAffected if The installed version cannot be determined to be 2023.1 or later
-
Verify patch statusCheck if IntelliJ IDEA has received updates: Help > Check for Updates, or check JetBrains release notes for the installed versionAffected if No update to version 2023.1 or later has been applied
The environment is affected if IntelliJ IDEA is installed with any version prior to 2023.1, regardless of whether specific Gradle or Maven project imports have been attempted.
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 · scoped2023.1
Upgrade IntelliJ IDEA to version 2023.1 or later to receive the fix that enforces the Trust Project confirmation for all project imports.
IntelliJ IDEA 2023.1 or later
- Back up your IntelliJ IDEA settings and any local projects if desired
- Download IntelliJ IDEA 2023.1 or later from the official JetBrains website at www.jetbrains.com/idea/download
- Install the new version, or use JetBrains Toolbox to update to the latest version
- Launch the updated IntelliJ IDEA and verify the "Trust Project" confirmation dialog appears when importing Gradle or Maven projects
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48431 — 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-48431 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