# CVE-2009-3457: Information disclosure in n/a

> Remote attackers can obtain sensitive intranet IP addresses via crafted HTTP requests to Cisco ACE XML Gateway and WAF.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2v43-c695-wqxw

## What is CVE-2009-3457?

CVE-2009-3457 is a medium-severity vulnerability in n/a, published on 29 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco ACE XML Gateway (AXG) and ACE Web Application Firewall (WAF) before 6.1 allow remote attackers to obtain sensitive information via an HTTP request that lacks a handler, as demonstrated by (1) an OPTIONS request or (2) a crafted GET request, leading to a Message-handling Errors message containing a certain client intranet IP address, aka Bug ID CSCtb82159.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2009-3457?

It affects 2 products.


Products: Cisco Ace Web Application Firewall, Cisco Ace Xml Gateway.

## How do I fix CVE-2009-3457?

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

## Is CVE-2009-3457 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3457 exists.

Public exploit code:

- Cisco ACE XML Gateway 6.0 - Internal IP Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3457 and fix it if it is affected.

What it is: CVE-2009-3457 is a medium-severity vulnerability in n/a, published on 29 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3457 exists.

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-2009-3457/ (Markdown: https://insights.sbomify.com/CVE-2009-3457/index.md)
```

## Sources

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

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