Security readout for executives and security teams
Plain-English summary
This issue affected JetBrains IntelliJ IDEA Ultimate application-server run configurations. When certain server configurations were running with defaults, a JMX service could listen on all network interfaces, creating a remote code execution risk. Exposure depends on using the affected IDE versions and having the configuration running and reachable.
Executive priority
Treat as a high-priority developer workstation and build-environment risk, especially where IDE-run servers are reachable from other hosts. Remediation is straightforward: update affected JetBrains IDE versions and reduce network exposure.
Technical view
CVE-2019-10104 concerns IntelliJ IDEA Ultimate Application Server run configurations for Tomcat, Jetty, Resin, or CloudBees. The vulnerable default caused a JMX server to bind beyond localhost. JetBrains fixed it in 2018.3.4, 2018.2.8, 2018.1.8, and 2017.3.7.
Likely exposure
Developers or build hosts running affected IntelliJ IDEA Ultimate versions with the listed Application Server configurations are the likely exposure. Risk rises if those machines are on untrusted or broadly reachable networks.
Exploitation context
The provided sources describe remote code execution potential, but do not provide evidence of exploitation in the wild. The CVE is not marked KEV in the bundle.
Researcher notes
The bundle lacks CVSS, CWE, and structured affected-product data, so analysis relies on the CVE description and JetBrains bulletin reference. Exposure is configuration-dependent and only applies while the relevant run configuration is active.
Mitigation direction
- Upgrade IntelliJ IDEA Ultimate to a fixed version or later.
- Review JetBrains' security bulletin for vendor guidance.
- Avoid running affected Application Server configurations on reachable networks.
- Ensure JMX services bind to localhost only.
- Restrict network access to developer workstations and build hosts.
Validation and detection
- Inventory IntelliJ IDEA Ultimate versions across developer and build systems.
- Identify use of Tomcat, Jetty, Resin, or CloudBees run configurations.
- Confirm affected configurations no longer expose JMX beyond localhost.
- Verify all installations are at fixed versions or later.
- Check whether vulnerable configurations were used on reachable networks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-10104 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://blog.jetbrains.com/blog/2019/06/19/jetbrains-security-bulletin-q1-2019/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.