# CVE-2002-0669: Denial of service in n/a

> Administrators can cause a denial of service on Pingtel xpressa phones by configuring SIP authentication schemes that fail silently.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2x83-cpgr-4rhm

## What is CVE-2002-0669?

CVE-2002-0669 is a medium-severity denial of service vulnerability in n/a, published on 11 Feb 2003. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The web interface for Pingtel xpressa SIP-based voice-over-IP phone 1.2.5 through 1.2.7.4 allows administrators to cause a denial of service by modifying the SIP_AUTHENTICATE_SCHEME value to force authentication of incoming calls, which does not notify the user when an authentication failure occurs.

## Which versions are affected by CVE-2002-0669?

It affects 1 product.


Products: Pingtel Xpressa.

## How do I fix CVE-2002-0669?

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

## Is CVE-2002-0669 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0667](https://insights.sbomify.com/CVE-2002-0667/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2002-0668](https://insights.sbomify.com/CVE-2002-0668/): Missing authorization in n/a (high 7.5)
- [CVE-2002-0670](https://insights.sbomify.com/CVE-2002-0670/): Information disclosure in n/a (high 7.5)
- [CVE-2002-0674](https://insights.sbomify.com/CVE-2002-0674/): Missing authorization in n/a (high 7.2)
- [CVE-2002-1934](https://insights.sbomify.com/CVE-2002-1934/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0669 and fix it if it is affected.

What it is: CVE-2002-0669 is a medium-severity denial of service vulnerability in n/a, published on 11 Feb 2003. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0669 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-2002-0669/ (Markdown: https://insights.sbomify.com/CVE-2002-0669/index.md)
```

## Sources

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

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