# CVE-2005-2181: Missing authorization in n/a

> Remote attackers can spoof notification messages on Cisco VoIP phones due to improper subscription verification, potentially misleading users about message status.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 10 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r2g9-49rq-6p4c

## What is CVE-2005-2181?

CVE-2005-2181 is a high-severity missing authorization vulnerability in n/a, published on 10 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco 7940/7960 Voice over IP (VoIP) phones do not properly check the Call-ID, branch, and tag values in a NOTIFY message to verify a subscription, which allows remote attackers to spoof messages such as the "Messages waiting" message.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 2 products.


Products: Cisco Ip Phone 7940 Firmware, Cisco Ip Phone 7960 Firmware.

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

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

## Is CVE-2005-2181 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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