CVE-2019-11029
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 · uneditedMirasys VMS before V7.6.1 and 8.x before V8.3.2 mishandles the Download() method of AutoUpdateService in SMServer.exe, leading to Directory Traversal. An attacker could use ..\ with this method to iterate over lists of interesting system files and download them without previous authentication. This includes SAM-database backups, Web.config files, etc. and might cause a serious impact on confidentiality.
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 confidenceThe Download() method of AutoUpdateService in SMServer.exe in Mirasys VMS before V7.6.1 and 8.x before 8.3.2 contains a directory traversal vulnerability. An unauthenticated attacker can use ..\ sequences in the Download() method to traverse the filesystem and download sensitive files including SAM database backups and Web.config files.
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< 7.6.1>= 8.0.0, < 8.3.2CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate SMServer.exeSearch for SMServer.exe in the installation directory (commonly C:\Program Files\Mirasys VMS\ or C:\Mirasys\). Check Program Files folders and any custom installation paths.Affected if SMServer.exe exists, indicating Mirasys VMS is installed
-
Determine VMS versionRight-click SMServer.exe, select Properties, then look at the Details tab for File Version. Alternatively, check the VMS client interface for the software version under Help > About.Affected if Version is below 7.6.1 OR between 8.0.0 and 8.3.1 inclusive (the vulnerable range)
-
Verify AutoUpdateService is accessibleCheck if TCP ports used by SMServer.exe (typically 80, 443, or 8080) are open to the network. Use netstat -an or a port scanner to confirm external accessibility.Affected if SMServer.exe is network-accessible (listening on non-localhost interfaces) and version is vulnerable
-
Confirm Download() method exposureAttempt a benign HTTP request to the Download endpoint (e.g., GET /Download?file=..\readme.txt). Use curl or a browser. A successful response indicates the path traversal is present.Affected if The Download() method responds to unauthenticated requests with directory traversal sequences (..\) and returns files outside the intended directory
A system is affected if Mirasys VMS with SMServer.exe version is below 7.6.1 or between 8.0.0 and 8.3.1 and the AutoUpdateService Download endpoint is network-accessible.
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 data7.6.18.3.2
Upgrade Mirasys VMS to version V7.6.1 or V8.3.2 or later to obtain the patched AutoUpdateService. Until patched, restrict network access to SMServer.exe using firewalls or network segmentation.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11029 — 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-2019-11029 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