Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2017-6752

HIGH · 7.5 CVSS v3.0 Published 2017-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A vulnerability in the web interface of the Cisco Adaptive Security Appliance (ASA) 9.3(3) and 9.6(2) could allow an unauthenticated, remote attacker to determine valid usernames. The attacker could use this information to conduct additional reconnaissance attacks. The vulnerability is due to the interaction between Lightweight Directory Access Protocol (LDAP) and SSL Connection Profile when they are configured together. An attacker could exploit the vulnerability by performing a username enumeration attack to the IP address of the device. An exploit could allow the attacker to determine valid usernames. Cisco Bug IDs: CSCvd47888.

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

A username enumeration vulnerability in Cisco ASA web interface allows unauthenticated remote attackers to determine valid usernames through interaction between LDAP and SSL Connection Profile when configured together. The attacker sends specially crafted requests to enumerate valid user accounts, which could enable further attacks like password spraying or credential theft.

MitigationApply the Cisco patch for bug CSCvd47888 (ASA updates 9.3(3) and 9.6(2) or later). If no patch available, review LDAP and SSL Connection Profile configuration to limit enumeration vectors or implement account lockout policies.

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
Adaptive Security Appliance SoftwareOperating system
Affected:= 9.3.3= 9.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco ASA device and version
    Log into the ASA CLI and run 'show version' to retrieve the software version, or check via ASDM under Home > Device Dashboard > Device Information
    Affected if The installed version is exactly 9.3.3 or 9.6.2
  2. Verify LDAP authentication is configured
    Run 'show run all ldap' or check in ASDM under Configuration > Device Management > LDAP to see if any LDAP server is defined for user authentication
    Affected if LDAP authentication is enabled and configured on the ASA
  3. Check for SSL VPN Connection Profile configuration
    Run 'show run tunnel-group' or check in ASDM under Configuration > Remote Access VPN > Clientless SSL VPN Access > Connection Profiles to see if any SSL VPN connection profiles exist
    Affected if An SSL VPN Connection Profile is configured
  4. Confirm web interface (ASDM) is accessible
    Attempt to access the ASA web interface at https://<ASA-IP>/ or verify 'http server enable' is configured and the management interface is reachable
    Affected if The ASDM/web interface is enabled and accessible from a network the attacker could reach

You are affected if your ASA runs version 9.3.3 or 9.6.2 AND has both LDAP authentication and an SSL VPN Connection Profile configured with the web interface accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch for bug CSCvd47888 (ASA updates 9.3(3) and 9.6(2) or later). If no patch available, review LDAP and SSL Connection Profile configuration to limit enumeration vectors or implement account lockout policies.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6752 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6752 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