# CVE-2003-1276: Weak cryptography in n/a

> Local attackers can read plaintext account numbers and weakly encrypted PINs from the registry to gain unauthorized access to NetTelephone accounts.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qpxc-fvhf-5gmq

## What is CVE-2003-1276?

CVE-2003-1276 is a medium-severity vulnerability in n/a, published on 16 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Netfone.exe of NetTelephone 3.5.6 uses weak encryption for user PIN's and stores user account numbers in plaintext in the HKEY_CURRENT_USER\Software\MediaRing.com\SDK\NetTelephone\settings registry key, which could allow local users to gain unauthorized access to NetTelephone accounts.

## Which versions are affected by CVE-2003-1276?

It affects 1 product.


Products: Nettelephone Nettelephone.

## How do I fix CVE-2003-1276?

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

## Is CVE-2003-1276 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1276 and fix it if it is affected.

What it is: CVE-2003-1276 is a medium-severity vulnerability in n/a, published on 16 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-1276 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-2003-1276/ (Markdown: https://insights.sbomify.com/CVE-2003-1276/index.md)
```

## Sources

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

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