CVE-2019-12373
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 · uneditedImproper access control and open directories in Ivanti LANDESK Management Suite (LDMS, aka Endpoint Manager) 10.0.1.168 Service Update 5 may lead to remote disclosure of administrator passwords.
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 confidenceImproper access control and open directory traversal vulnerabilities in Ivanti LANDESK Management Suite 10.0.1.168 Service Update 5 allow remote unauthenticated attackers to access sensitive files, potentially exposing administrator credentials stored on the server.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify installed LANDESK Management Suite versionCheck the installed version through the LANDESK console or by inspecting the program's version information. This is typically found in the control panel, the LANDESK About section, or by querying the LANDESK core server services.Affected if The installed version is exactly 10.0.1.168 (Service Update 5)
-
Determine if the web component is accessibleIdentify whether the LANDESK web console or any web services are exposed. Check network configuration to see if the LANDESK web ports (typically 80/443 or custom configured ports) are reachable from outside the local network.Affected if The LANDESK web interface is exposed to untrusted networks or the internet without proper network segmentation or authentication proxies
-
Test for directory traversal vulnerabilityIf the web interface is accessible, attempt to access a known directory path using traversal sequences (e.g., /..\ or /../) to see if the server allows navigation outside the intended web root directory.Affected if The server allows directory traversal and returns file contents or directory listings outside the expected scope
-
Review access logs for suspicious file access patternsExamine LANDESK web server and IIS logs for unusual requests containing directory traversal patterns or attempts to access sensitive paths such as configuration files, credential stores, or system directories.Affected if Logs show unauthorized access attempts to sensitive files or directory traversal patterns from external IP addresses
A system is affected if it runs LANDESK Management Suite version 10.0.1.168 with the web component exposed to network access.
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 dataApply vendor patches or upgrade to a patched version of LANDESK Management Suite; audit exposed systems for compromise and rotate compromised administrator credentials immediately.
- 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-2019-12373 — 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-12373 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