# CVE-2002-0394: Weak cryptography in n/a

> Red-M Bluetooth Access Points use case-insensitive passwords, reducing entropy and facilitating brute-force attacks against authentication.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mhc5-fg7c-fv68

## What is CVE-2002-0394?

CVE-2002-0394 is a critical vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red-M 1050 (Bluetooth Access Point) uses case insensitive passwords, which makes it easier for attackers to conduct a brute force guessing attack due to the smaller space of possible passwords.

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

It affects 1 product.


Products: Red-M 1050ap Lan Acess Point.

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

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

## Is CVE-2002-0394 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0395](https://insights.sbomify.com/CVE-2002-0395/): Missing authorization in n/a (critical 10.0)
- [CVE-2002-0398](https://insights.sbomify.com/CVE-2002-0398/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0393](https://insights.sbomify.com/CVE-2002-0393/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0396](https://insights.sbomify.com/CVE-2002-0396/): Auth bypass in n/a (high 7.5)
- [CVE-2002-0397](https://insights.sbomify.com/CVE-2002-0397/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0394 is a critical vulnerability in n/a, published on 2 Apr 2003. 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-2002-0394 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-0394/ (Markdown: https://insights.sbomify.com/CVE-2002-0394/index.md)
```

## Sources

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

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