dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2019-10104

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-03
Fix available
A fix is available. Upgrade to 2018.1.8 / 2018.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In several JetBrains IntelliJ IDEA Ultimate versions, an Application Server run configuration (for Tomcat, Jetty, Resin, or CloudBees) with the default setting allowed a remote attacker to execute code when the configuration is running, because a JMX server listened on all interfaces instead of localhost only. The issue has been fixed in the following versions: 2018.3.4, 2018.2.8, 2018.1.8, and 2017.3.7.

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 confidence

In several JetBrains IntelliJ IDEA Ultimate versions, Application Server run configurations for Tomcat, Jetty, Resin, or CloudBees had a default setting where the JMX server listened on all network interfaces (0.0.0.0) instead of localhost only. This exposed the JMX service to remote network access, allowing remote attackers to execute arbitrary code when the configuration was running.

MitigationUpgrade IntelliJ IDEA Ultimate to version 2018.3.4, 2018.2.8, 2018.1.8, 2017.3.7 or later, which restricts JMX to localhost by default. Alternatively, manually configure JMX to bind only to localhost (127.0.0.1) in server run configurations.

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
Intellij IdeaApplication
Affected:>= 2018.1, < 2018.1.8>= 2018.2, < 2018.2.8>= 2018.3, < 2018.3.4>= 2018.3.5, < 2018.3.7

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IntelliJ IDEA version
    Open IntelliJ IDEA and go to Help > About to view the installed version, or check the version file in the installation directory
    Affected if The version is 2018.1.x before 2018.1.8, 2018.2.x before 2018.2.8, 2018.3.x before 2018.3.4, or 2018.3.5-2018.3.6
  2. Identify Application Server run configurations
    Open Run > Edit Configurations and look for any configurations using Tomcat, Jetty, Resin, or CloudBees application servers
    Affected if Any such run configuration exists in the project
  3. Examine JMX binding in run configuration
    In the run configuration settings for the application server, locate the JMX configuration section and check the 'Host' or 'Bind Address' setting
    Affected if The JMX host is set to 0.0.0.0 or a value that allows external network access rather than localhost or 127.0.0.1

You are affected if your IntelliJ IDEA version falls within the vulnerable ranges AND you have an application server run configuration with JMX bound to all network interfaces instead of localhost.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2018.1.8 / 2018.2.8 / 2018.3.4 or later
Fixed in 2018.1.82018.2.82018.3.4
Interim mitigation

Upgrade IntelliJ IDEA Ultimate to version 2018.3.4, 2018.2.8, 2018.1.8, 2017.3.7 or later, which restricts JMX to localhost by default. Alternatively, manually configure JMX to bind only to localhost (127.0.0.1) in server run configurations.

Recommended fix High confidence

Upgrade to IntelliJ IDEA 2018.3.7 or later (or 2018.2.8, 2018.1.8, or 2017.3.7 as alternatives)

  1. 1. Close IntelliJ IDEA if it is currently running
  2. 2. Download IntelliJ IDEA version 2018.3.7 or later from the official JetBrains website (jetbrains.com/idea)
  3. 3. Run the installer and follow the installation wizard prompts
  4. 4. If prompted, choose to overwrite the existing installation
  5. 5. After installation, open IntelliJ IDEA
  6. 6. Verify the version by going to Help > About to confirm the installed version is 2018.3.7 or later
  7. 7. When using Application Server run configurations (for Tomcat, Jetty, Resin, or CloudBees), ensure the JMX listener is configured to bind to localhost only rather than all network interfaces
Caveat Minor: Users on older 2018.x versions should test their Application Server run configurations after upgrading to ensure JMX behavior meets expectations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10104 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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