# CVE-2007-0057: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access to Cisco Clean Access devices due to a shared secret authentication key that is not properly configured or modifiable.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c8f3-cw65-hxxc

## What is CVE-2007-0057?

CVE-2007-0057 is a critical vulnerability in n/a, published on 4 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Clean Access (CCA) 3.6.x through 3.6.4.2 and 4.0.x through 4.0.3.2 does not properly configure or allow modification of a shared secret authentication key, which causes all devices to have the same shared sercet and allows remote attackers to gain unauthorized access.

Weakness: CWE-255

## Which versions are affected by CVE-2007-0057?

It affects 1 product.


Products: Cisco Network Admission Control Manager and Server System Software.

## How do I fix CVE-2007-0057?

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

## Is CVE-2007-0057 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4332](https://insights.sbomify.com/CVE-2005-4332/): Auth bypass in n/a (critical 9.4)
- [CVE-2007-0058](https://insights.sbomify.com/CVE-2007-0058/): Auth bypass in n/a (high 7.8)
- [CVE-2013-1177](https://insights.sbomify.com/CVE-2013-1177/): SQL injection in n/a (high 7.5)
- [CVE-2005-2631](https://insights.sbomify.com/CVE-2005-2631/): Auth bypass in n/a (high 7.5)
- [CVE-2005-4825](https://insights.sbomify.com/CVE-2005-4825/): Auth bypass in n/a (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0057 and fix it if it is affected.

What it is: CVE-2007-0057 is a critical vulnerability in n/a, published on 4 Jan 2007. 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-2007-0057 in the wild and no public exploit code.

Affected product: n/a. 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-2007-0057/ (Markdown: https://insights.sbomify.com/CVE-2007-0057/index.md)
```

## Sources

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

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