dbcve.org
Mds PulsenetApplication · Ge

CVE-2018-10611

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-04
Fix available
A fix is available. Upgrade to after 3.2.1 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
Java remote method invocation (RMI) input port in GE MDS PulseNET and MDS PulseNET Enterprise version 3.2.1 and prior may be exploited to allow unauthenticated users to launch applications and support remote code execution through web services.

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

GE MDS PulseNET versions 3.2.1 and prior expose a Java RMI input port that lacks authentication controls. Unauthenticated attackers can leverage this RMI interface to execute arbitrary code through web services, achieving remote code execution on affected systems.

MitigationRestrict network access to the vulnerable RMI port through firewall rules or network segmentation; if available, apply vendor patches to upgrade beyond version 3.2.1.

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
Mds PulsenetApplication
Affected:<= 3.2.1

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. Identify if GE MDS PulseNET is installed
    Locate the PulseNET installation directory on the system, typically found in Program Files or a dedicated application folder. Check for executables or services named PulseNET, MDS, or containing 'pulsenet' in the filename.
    Affected if The software is present on the system
  2. Determine the installed version
    Locate version information in the installation directory, check application metadata files, or run the application with a version flag if available. Common locations include an about dialog, a version.info file, or the executable properties.
    Affected if The installed version is 3.2.1 or any version lower than 3.2.1
  3. Identify the RMI service port configuration
    Examine configuration files in the PulseNET installation directory for RMI-related settings. Look for files named config.xml, rmi.config, or similar that specify the RMI registry port (commonly port 1099 by default for Java RMI).
    Affected if RMI configuration exists and specifies a listening port
  4. Verify network accessibility of the RMI port
    Use netstat, nmap, or similar network tools to determine if the identified RMI port is listening on network interfaces accessible from outside the local system. Check both the configured port and common default RMI ports.
    Affected if The RMI port is listening on a non-loopback interface and is reachable from the network

A system is affected if GE MDS PulseNET version 3.2.1 or lower is installed and the RMI service port is accessible on the network.

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 a release after 3.2.1
Interim mitigation

Restrict network access to the vulnerable RMI port through firewall rules or network segmentation; if available, apply vendor patches to upgrade beyond version 3.2.1.

Recommended fix Moderate confidence

MDS PulseNET > 3.2.1 (contact GE Grid Solutions for exact fixed version)

  1. Contact GE Grid Solutions directly to obtain the latest fixed version of MDS PulseNET
  2. Request CVE-2018-10611 patched version information and upgrade package
  3. Plan maintenance window for the upgrade process
  4. Backup all current PulseNET configurations and data
  5. Upgrade MDS PulseNET to the latest version provided by GE Grid Solutions
  6. Verify the Java RMI port is no longer exposed or is properly secured post-upgrade
  7. Test that all expected PulseNET functionality works correctly after upgrade
  8. Confirm with GE Grid Solutions that the specific RMI authentication vulnerability is resolved in the new version
Caveat Unknown from available advisory - verify with vendor during upgrade consultation

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

Fix this in Mds Pulsenet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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