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

> Remote attackers can bypass authentication to access administrative interfaces or WLANs on Aruba and Alcatel-Lucent wireless controllers.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-37c7-c3v8-w5p9

## What is CVE-2007-0932?

CVE-2007-0932 is a high-severity authentication bypass vulnerability in n/a, published on 14 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The (1) Aruba Mobility Controllers 200, 600, 2400, and 6000 and (2) Alcatel-Lucent OmniAccess Wireless 43xx and 6000 do not properly implement authentication and privilege assignment for the guest account, which allows remote attackers to access administrative interfaces or the WLAN.

Weakness: CWE-264

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

It affects 2 products.


Products: Alcatel-Lucent Omniaccess Wireless, Aruba Mobility Controller.

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

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

## Is CVE-2007-0932 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0931](https://insights.sbomify.com/CVE-2007-0931/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0932 is a high-severity authentication bypass vulnerability in n/a, published on 14 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0932 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-0932/ (Markdown: https://insights.sbomify.com/CVE-2007-0932/index.md)
```

## Sources

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

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