dbcve.org
MpsApplication · Jetbrains

CVE-2019-18362

MEDIUM · 5.3 CVSS v3.1 Published 2019-10-31
Fix available
A fix is available. Upgrade to 2019.2.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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
JetBrains MPS before 2019.2.2 exposed listening ports to the network.

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 · moderate confidence

JetBrains MPS before version 2019.2.2 bound its internal listening ports to all network interfaces rather than restricting them to localhost. This allowed remote attackers on the network to connect to these exposed ports, potentially accessing internal functionality or launching further attacks.

MitigationUpgrade JetBrains MPS to version 2019.2.2 or later, which addresses the port binding issue by restricting listening ports to local connections only.

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
MpsApplication
Affected:< 2019.2.2

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Identify JetBrains MPS installation and version
    Locate the JetBrains MPS installation directory and check the version file or product metadata (often in the MPS installation root or about dialog)
    Affected if The installed version is any version prior to 2019.2.2
  2. Verify version number against affected range
    Compare the identified version to 2019.2.2 - if it is lower (e.g., 2019.2, 2019.1, 2018.x, etc.), the instance is within the affected range
    Affected if The version number is less than 2019.2.2
  3. Inspect network port bindings
    Use system network tools (netstat, ss, or similar) to examine which addresses MPS-related processes are listening on - look for bindings to 0.0.0.0 or external interfaces rather than 127.0.0.1 localhost
    Affected if MPS listening ports are bound to 0.0.0.0 or all interfaces instead of localhost only

The environment is affected if JetBrains MPS version is below 2019.2.2 AND the application has its internal ports exposed to non-localhost addresses.

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.

From vendor data
Upgrade available Upgrade to 2019.2.2 or later
Fixed in 2019.2.2
Interim mitigation

Upgrade JetBrains MPS to version 2019.2.2 or later, which addresses the port binding issue by restricting listening ports to local connections only.

Fix this in Mps Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18362 — 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-18362 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