# CVE-2017-6752: Information disclosure in Cisco Adaptive Security Appliance

> Unauthenticated attackers can enumerate valid usernames via the web interface when LDAP and SSL profiles are configured, aiding further reconnaissance.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wvc6-xr2j-qjmh

## What is CVE-2017-6752?

CVE-2017-6752 is a high-severity vulnerability in Cisco Adaptive Security Appliance Software, published on 7 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-6752?

It affects 1 product.


Products: Cisco Adaptive Security Appliance Software.

## How do I fix CVE-2017-6752?

No fix has been published for CVE-2017-6752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6752 being exploited?

There is no known exploitation of CVE-2017-6752 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Adaptive Security Appliance Software

- [CVE-2025-20333](https://insights.sbomify.com/CVE-2025-20333/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow (critical 9.9, exploited in the wild)
- [CVE-2016-6366](https://insights.sbomify.com/CVE-2016-6366/): Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2026-20349](https://insights.sbomify.com/CVE-2026-20349/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Heap Inspection (high 8.6, exploited in the wild)
- [CVE-2024-20353](https://insights.sbomify.com/CVE-2024-20353/): Cisco ASA and FTD Denial of Service (high 8.6, exploited in the wild)
- [CVE-2016-6367](https://insights.sbomify.com/CVE-2016-6367/): Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6752 and fix it if it is affected.

What it is: CVE-2017-6752 is a high-severity vulnerability in Cisco Adaptive Security Appliance Software, published on 7 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6752 in the wild and no public exploit code.

Affected product: Cisco Adaptive Security Appliance Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6752/ (Markdown: https://insights.sbomify.com/CVE-2017-6752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6752
- OSV: https://osv.dev/vulnerability/CVE-2017-6752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6752/
Summaries are generated and may contain mistakes; the official description above is the record.