# CVE-2007-5791: Auth bypass in n/a

> Remote attackers can spoof SIP INVITE messages to cause denial of service or inject malicious content into calls due to improper origin verification.

- **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:** 1 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cq34-q55h-g2x8

## What is CVE-2007-5791?

CVE-2007-5791 is a critical authentication bypass vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Vonage Motorola Phone Adapter VT 2142-VD does not properly verify that a SIP INVITE message originated from a legitimate server, which allows remote attackers to send spoofed INVITE messages, as demonstrated by a flood of messages triggering a denial of service, and by phone calls with malicious content.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Vonage Motorola Phone Adapter Vt2142-Vd.

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

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

## Is CVE-2007-5791 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5792](https://insights.sbomify.com/CVE-2007-5792/): Weak cryptography in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5791 is a critical authentication bypass vulnerability in n/a, published on 1 Nov 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-5791 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-5791/ (Markdown: https://insights.sbomify.com/CVE-2007-5791/index.md)
```

## Sources

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

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