# CVE-2002-1934: Information disclosure in n/a

> Attackers can obtain sensitive MD5 password hashes and registration data from Pingtel xpressa VoIP phones during boot-up.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9x4q-mqv8-f9qg

## What is CVE-2002-1934?

CVE-2002-1934 is a medium-severity vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pingtel xpressa SIP-based voice-over-IP phone 1.2.5 through 2.0.1 leaks sensitive information during boot-up, which allows attackers to obtain the MD5 hash of the Admin password, MD5 hash of the physical password, and other registration information.

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

It affects 1 product.


Products: Pingtel Xpressa.

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

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

## Is CVE-2002-1934 being exploited?

There is no known exploitation of CVE-2002-1934 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-1935](https://insights.sbomify.com/CVE-2002-1935/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1934 is a medium-severity vulnerability in n/a, published on 28 Jun 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-2002-1934 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-1934/ (Markdown: https://insights.sbomify.com/CVE-2002-1934/index.md)
```

## Sources

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

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