dbcve.org
AvalancheApplication · Ivanti

CVE-2018-8901

HIGH · 7.8 CVSS v3.0 Published 2018-06-29
Fix available
A fix is available. Upgrade to after 6.2 or later.
See remediation →
80/100
Remediation priority · High
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
An issue was discovered in Ivanti Avalanche for all versions between 5.3 and 6.2. A local user with database access privileges can read the encrypted passwords for users who authenticate via LDAP to Avalanche services. These passwords are stored in the Avalanche databases. This issue only affects customers who have enabled LDAP authentication in their configuration.

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 confidence

Local users with database access privileges can read encrypted passwords for LDAP-authenticated users stored in Ivanti Avalanche databases (versions 5.3-6.2). The vulnerability stems from insufficient protection of stored LDAP credentials in the Avalanche database, allowing privilege escalation via credential theft.

MitigationRestrict database access to only trusted administrators, rotate exposed LDAP passwords, and upgrade Ivanti Avalanche to a version beyond 6.2 that addresses the insecure credential storage.

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
AvalancheApplication
Affected:>= 5.3, <= 6.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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. Determine Ivanti Avalanche version
    Check the installed version of Ivanti Avalanche on the system using installed programs list, or check the Avalanche server console for version information.
    Affected if Installed version is 5.3, 5.4, 5.5, 6.0, 6.1, or 6.2
  2. Confirm LDAP authentication is enabled
    Access Avalanche administration console or examine configuration files to verify if LDAP user authentication is configured and active.
    Affected if LDAP authentication integration is configured for Avalanche user or administrator access
  3. Review database file access permissions
    Examine file system permissions on the Avalanche database directory and files to determine if standard local users can read database contents.
    Affected if Database files are readable by non-administrative user accounts

Environment is affected if running Ivanti Avalanche versions 5.3-6.2 with LDAP authentication enabled and the database is accessible to non-privileged local users.

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.

From vendor data
Upgrade available Upgrade to a release after 6.2
Interim mitigation

Restrict database access to only trusted administrators, rotate exposed LDAP passwords, and upgrade Ivanti Avalanche to a version beyond 6.2 that addresses the insecure credential storage.

Fix this in Avalanche Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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