CVE-2022-48433
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 the NTLM hash could leak through an API method used in the IntelliJ IDEA built-in web server.
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 versions before 2023.1, an API method in the built-in web server can inadvertently expose NTLM authentication hashes. This credential leakage occurs through the IDE's internal web server functionality, allowing potential authentication bypass or credential harvesting by attackers who can access the exposed hashes.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify IntelliJ IDEA installed versionOpen IntelliJ IDEA and go to Help > About, or check the installation directory for version information. On Windows, this is typically in C:\Program Files\JetBrains\IntelliJ IDEA\. On macOS, check /Applications/IntelliJ IDEA.app. Compare the version number to the affected range: versions before 2023.1 are vulnerable.Affected if The installed version is any release prior to 2023.1 (for example, 2022.3, 2022.2, 2022.1, etc.)
-
Determine if built-in web server is activeIntelliJ IDEA runs an internal web server for various IDE features. Check if the IDE is running and has recently served requests. Look for listening ports in the IDE's internal network settings or examine active network connections associated with the IDEA process.Affected if The built-in web server has been active or is currently running while using a vulnerable version
-
Verify NTLM authentication usageReview the IDE's authentication settings or any integrated services that may use NTLM authentication. Check browser or external tool connections to the IDE that might leverage NTLM for proxy or authentication purposes.Affected if NTLM authentication is configured or in use with the IDE's built-in web server functionality
You are affected if you run any IntelliJ IDEA version before 2023.1 and the IDE's built-in web server has been active while NTLM authentication was in use, as this combination enables the credential hash exposure.
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 obtain the patched version. If immediate upgrade is not feasible, restrict network access to the IDE's built-in web server and consider disabling NTLM authentication where possible.
IntelliJ IDEA 2023.1 or later
- 1. Back up your current IntelliJ IDEA projects and settings
- 2. Download IntelliJ IDEA 2023.1 or later from the official JetBrains website (www.jetbrains.com)
- 3. Install the new version over your current installation or to a new location
- 4. Import your backed-up settings if needed
- 5. Verify the built-in web server no longer exposes NTLM hashes through API methods
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-48433 — 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-48433 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