# CVE-2007-6226: Auth bypass in n/a

> Remote attackers can bypass authentication on APC PDUs by exploiting a race condition during concurrent login attempts, gaining unauthorized administrative access.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p5cg-5vq8-4j3h

## What is CVE-2007-6226?

CVE-2007-6226 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The American Power Conversion (APC) AP7932 0u 30amp Switched Rack Power Distribution Unit (PDU), with rpdu 3.5.5 and aos 3.5.6, allows remote attackers to bypass authentication and obtain login access by making a login attempt while a different client is logged in, and then resubmitting the login attempt once the other client exits.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2007-6226?

It affects 2 products.


Products: Apc Oas, Apc Switched Rack Pdu Firmware.

## How do I fix CVE-2007-6226?

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

## Is CVE-2007-6226 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6226 and fix it if it is affected.

What it is: CVE-2007-6226 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-6226 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-2007-6226/ (Markdown: https://insights.sbomify.com/CVE-2007-6226/index.md)
```

## Sources

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

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