# CVE-2007-3347: Missing authorization in n/a

> Remote attackers can bypass IP restrictions to send arbitrary SIP messages, enabling forged caller ID and unauthorized communication with the device.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:C/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:** 22 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w8vh-crmm-4pp5

## What is CVE-2007-3347?

CVE-2007-3347 is a high-severity missing authorization vulnerability in n/a, published on 22 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The D-Link DPH-540/DPH-541 phone accepts SIP INVITE messages that are not from the Call Server's IP address, which allows remote attackers to engage in arbitrary SIP communication with the phone, as demonstrated by communication with forged caller ID.

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

It affects 2 products.


Products: D-Link Dph-540, D-Link Dph-541.

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

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

## Is CVE-2007-3347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3348](https://insights.sbomify.com/CVE-2007-3348/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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