CVE-2018-10615
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 · uneditedDirectory traversal may lead to files being exfiltrated or deleted on the GE MDS PulseNET and MDS PulseNET Enterprise version 3.2.1 and prior host platform.
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 confidenceThis is a path traversal vulnerability in GE MDS PulseNET (enterprise network management software). The flaw allows attackers to use directory traversal sequences (e.g., ../) in requests to access files outside the web application's root directory, potentially leading to unauthorized file exfiltration or deletion on the host system.
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<= 3.2.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 GE MDS PulseNET installationCheck for the PulseNET application on the system - look for installation directories named 'PulseNET' or 'MDS PulseNET', or check Windows Services for 'PulseNET' or 'MDS' related services. On Linux, check /opt or common application directories.Affected if The product is installed and accessible on the network
-
Determine installed versionLocate the PulseNET installation directory and look for version information in About dialogs, README files, or version manifests. Common locations include the program's main executable or a version.txt file in the installation root.Affected if Installed version is 3.2.1 or lower
-
Verify web interface is exposedConfirm that the PulseNET web interface (HTTP/HTTPS) is accessible from network locations. Check if the web service is running and bound to a network interface, not just localhost.Affected if Web interface is accessible on network and version is <= 3.2.1
-
Check web server configurationExamine the PulseNET web server configuration files (typically in the web or http subdirectory of the installation) to verify whether input validation or path sanitization is implemented on file request parameters.Affected if No input validation on file parameters and version is <= 3.2.1
User is affected if GE MDS PulseNET version 3.2.1 or lower is installed with its web interface accessible on the network, and the file request parameters lack traversal sequence validation.
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.
From vendor dataImplement strict input validation and path sanitization on all file access parameters to prevent traversal sequences; restrict file system permissions to limit potential damage if exploitation occurs; upgrade to a patched version if available from GE.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10615 — 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-2018-10615 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