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

> Remote attackers can bypass authorization policies in BEA AquaLogic Service Bus by sending malformed requests, gaining unauthorized access to back-end services.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wq7v-6qc2-955r

## What is CVE-2007-0432?

CVE-2007-0432 is a high-severity authentication bypass vulnerability in n/a, published on 23 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BEA AquaLogic Service Bus 2.0, 2.1, and 2.5 does not properly reject malformed request messages to a proxy service, which might allow remote attackers to bypass authorization policies and route requests to back-end services or conduct other unauthorized activities.

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

It affects 1 product.


Products: Bea Aqualogic Service Bus.

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

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

## Is CVE-2007-0432 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0433](https://insights.sbomify.com/CVE-2007-0433/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0432 is a high-severity authentication bypass vulnerability in n/a, published on 23 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0432 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-0432/ (Markdown: https://insights.sbomify.com/CVE-2007-0432/index.md)
```

## Sources

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

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