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

> Remote attackers can send SIP INVITE requests to Avaya IP phones without authentication, leading to unspecified impacts.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 21 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5982-ff7w-wx53

## What is CVE-2007-3320?

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

### Official description

The Avaya 4602SW IP Phone (Model 4602D02A) with 2.2.2 and earlier SIP firmware accepts SIP INVITE requests from arbitrary source IP addresses, which allows remote attackers to have an unspecified impact.

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

It affects 1 product.


Products: Avaya 4602sw Ip Phone.

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

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

## Is CVE-2007-3320 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3319](https://insights.sbomify.com/CVE-2007-3319/): Weak cryptography in n/a (high 7.5)
- [CVE-2007-3321](https://insights.sbomify.com/CVE-2007-3321/): Denial of service in n/a (medium 5.0)
- [CVE-2007-3322](https://insights.sbomify.com/CVE-2007-3322/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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