# CVE-2011-4500: Misconfiguration in n/a

> Remote attackers can administer the firewall via SOAP requests if UPnP is enabled, exposing the WAN port to unauthorized control.

- **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:** 22 Nov 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q2fp-xmhf-wjcx

## What is CVE-2011-4500?

CVE-2011-4500 is a high-severity vulnerability in n/a, published on 22 Nov 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UPnP IGD implementation on the Cisco Linksys WRT54GX with firmware 2.00.05, when UPnP is enabled, configures the SOAP server to listen on the WAN port, which allows remote attackers to administer the firewall via SOAP requests.

Weakness: CWE-16

## Which versions are affected by CVE-2011-4500?

It affects 2 products.


Products: Cisco Linksys Wrt54gx Router Firmware, Linksys Wrt54gx.

## How do I fix CVE-2011-4500?

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

## Is CVE-2011-4500 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4500 and fix it if it is affected.

What it is: CVE-2011-4500 is a high-severity vulnerability in n/a, published on 22 Nov 2011. 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-2011-4500 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-2011-4500/ (Markdown: https://insights.sbomify.com/CVE-2011-4500/index.md)
```

## Sources

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

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