# CVE-2011-4499: Missing authorization in n/a

> Remote attackers can bypass security controls to create arbitrary port mappings on Linksys routers via UPnP, exposing internal 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:** 22 Nov 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-f493-r5jh-m3rp

## What is CVE-2011-4499?

CVE-2011-4499 is a high-severity missing authorization 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 in the Broadcom UPnP stack on the Cisco Linksys WRT54G with firmware before 4.30.5, WRT54GS v1 through v3 with firmware before 4.71.1, and WRT54GS v4 with firmware before 1.06.1 allows remote attackers to establish arbitrary port mappings by sending a UPnP AddPortMapping action in a SOAP request to the WAN interface, related to an "external forwarding" vulnerability.

Weakness: CWE-16

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

It affects 4 products.


Products: Cisco Linksys Wrt54g Router Firmware, Cisco Linksys Wrt54gs Router Firmware, Linksys Wrt54g, Linksys Wrt54gs.

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

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

## Is CVE-2011-4499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4499 is a high-severity missing authorization 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-4499 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-4499/ (Markdown: https://insights.sbomify.com/CVE-2011-4499/index.md)
```

## Sources

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

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