CVE-2019-12375
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 · uneditedOpen directories in Ivanti LANDESK Management Suite (LDMS, aka Endpoint Manager) 10.0.1.168 Service Update 5 may lead to remote information disclosure and arbitrary code execution.
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 confidenceIvanti LANDESK Management Suite 10.0.1.168 Service Update 5 has open directory listings enabled in its web component, allowing remote attackers to browse and access sensitive files on the server filesystem, potentially leading to information disclosure and arbitrary code execution.
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= 10.0.1.168CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
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.
-
Confirm the LANDESK Management Suite versionOpen the LANDESK console or check the installed software version on the server. On Windows, this may be visible in Add/Remove Programs or in the About section of the LANDESK console.Affected if The installed version is exactly 10.0.1.168 (Service Update 5)
-
Identify if the web component is installed and runningCheck if the LANDESK Web Server or LDMS Web services are installed and running on the server. Look for IIS websites or the built-in LANDESK web service process.Affected if The web component is installed and accessible on the network
-
Test for directory listing disclosureUsing a web browser or curl command, navigate to common LANDESK web paths such as the root of the web server or subdirectories like /landesk/, /ldms/, or /web/. Observe whether directory indexes are displayed showing file listings.Affected if Directory listings are displayed and files can be browsed without authentication or explicit file access
-
Check web server configuration for directory browsing settingsIf using IIS, check the web.config file or IIS Manager for the directoryBrowse setting. Look for 'enableDefaultDoc' and directory browsing settings in the web server configuration files.Affected if Directory browsing is explicitly enabled in the web server configuration
A system is affected if it runs LANDESK Management Suite version 10.0.1.168 and has the web component enabled with directory listing functionality exposed to network users.
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 dataDisable directory browsing/listings in the LDMS web server configuration and restrict file access permissions. If a vendor patch is available, apply it. Consider network segmentation to limit exposure.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12375 — 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-12375 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