# CVE-2005-3803: Hardcoded credentials in n/a

> Hard-coded SNMP community strings in Cisco IP Phones allow remote attackers to obtain sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 24 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vfj7-xg8w-82vp

## What is CVE-2005-3803?

CVE-2005-3803 is a high-severity vulnerability in n/a, published on 24 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco IP Phone (VoIP) 7920 1.0(8) contains certain hard-coded ("fixed") public and private SNMP community strings that cannot be changed, which allows remote attackers to obtain sensitive information.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2005-3803?

It affects 1 product.


Products: Cisco Unified Wireless Ip Phone 7920 Firmware.

## How do I fix CVE-2005-3803?

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

## Is CVE-2005-3803 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3803 and fix it if it is affected.

What it is: CVE-2005-3803 is a high-severity vulnerability in n/a, published on 24 Nov 2005. 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-2005-3803 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-2005-3803/ (Markdown: https://insights.sbomify.com/CVE-2005-3803/index.md)
```

## Sources

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

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