# CVE-2004-2080: Other in n/a

> Red-Alert fails to correctly identify SSIDs containing multiple spaces, potentially leading to inaccurate wireless network monitoring results.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 19 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6p95-xr36-cvr7

## What is CVE-2004-2080?

CVE-2004-2080 is a medium-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red-M Red-Alert 2.7.5 with software 3.1 build 24 converts multiple spaces in a Service Set Identifier (SSID) to a single space, which prevents Red-Alert from correctly identifying the SSID.

## Which versions are affected by CVE-2004-2080?

It affects 1 product.


Products: Red-M Red-Alert.

## How do I fix CVE-2004-2080?

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

## Is CVE-2004-2080 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2079](https://insights.sbomify.com/CVE-2004-2079/): Auth bypass in n/a (high 7.5)
- [CVE-2004-2078](https://insights.sbomify.com/CVE-2004-2078/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2080 and fix it if it is affected.

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

## Sources

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

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