dbcve.org
Br 6104k Router FirmwareOperating system · Edimax

CVE-2011-4501

HIGH · 10.0 CVSS v2.0 Published 2011-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg, Canyon-Tech CN-WF512 with firmware 1.83, Canyon-Tech CN-WF514 with firmware 2.08, Sitecom WL-153 with firmware before 1.39, and Sweex LB000021 with firmware 3.15 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple router models (Edimax BR-6104K, Edimax 6114Wg, Canyon-Tech CN-WF512/514, Sitecom WL-153, Sweex LB000021) have UPnP IGD exposed on the WAN interface without authentication, allowing remote attackers to send SOAP AddPortMapping requests that create arbitrary port forwarding rules from the internet to internal network devices.

MitigationDisable UPnP functionality on the WAN interface or block external access to UPnP ports (1900/UDP) at the perimeter firewall; update affected devices to patched firmware versions where available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Br 6104k Router FirmwareOperating system
Affected:= 3.21
Br 6104kHardware / appliance
Affected:all versions
Cn Wf512 Router FirmwareOperating system
Affected:= 1.83
Cn Wf514 Router FirmwareOperating system
Affected:= 2.08
Cn Wf512Hardware / appliance
Affected:all versions
Cn Wf514Hardware / appliance
Affected:all versions
6114wg Router FirmwareOperating system
Affected:= 1.83= 2.08
6114wgHardware / appliance
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router's web administration interface (typically at 192.168.1.1 or 192.168.0.1) and locate the device information or status page to confirm the exact model number
    Affected if The device is one of: Edimax BR-6104K, Edimax 6114WG, Canyon-Tech CN-WF512, Canyon-Tech CN-WF514, Sitecom WL-153, or Sweex LB000021
  2. Check the firmware version
    In the router's web interface, navigate to the firmware or system information section and note the installed firmware version number
    Affected if The firmware version matches one listed in affected versions or is any version for models noted as 'all versions'
  3. Verify UPnP is enabled on the WAN interface
    In the router's web interface, locate the UPnP settings (usually under Advanced, NAT, or Port Forwarding settings) and confirm whether UPnP IGD is enabled and whether it applies to the WAN connection
    Affected if UPnP IGD is enabled and configured to operate on the WAN (external) interface
  4. Test for external UPnP accessibility
    From an external network (not behind the router), use a UDP port scanner or simple tool to send a packet to the router's public IP address on port 1900 (the UPnP SSDP multicast port) and observe if a response is received
    Affected if The router responds to UPnP SSDP queries on port 1900/UDP from the WAN side, indicating UPnP is exposed externally

A user is affected if they own one of the listed router models, the device has UPnP IGD enabled on the WAN interface, and port 1900/UDP is accessible from the internet.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable UPnP functionality on the WAN interface or block external access to UPnP ports (1900/UDP) at the perimeter firewall; update affected devices to patched firmware versions where available.

Recommended fix Moderate confidence

Edimax BR-6104K: firmware 3.25+ | Sitecom WL-153: firmware 1.39+ | Other models: contact vendor for fixed firmware

  1. 1. Identify the exact router model from the affected list (BR-6104K, 6114Wg, CN-WF512, CN-WF514, WL-153, or LB000021)
  2. 2. Access the router's web administration interface via LAN connection
  3. 3. Navigate to the firmware or system settings section to check the current firmware version
  4. 4. For Edimax BR-6104K: Download firmware version 3.25 or later from the official Edimax support website
  5. 5. For Sitecom WL-153: Download firmware version 1.39 or later from the official Sitecom support website
  6. 6. For Canyon-Tech CN-WF512/CN-WF514: Check vendor for firmware updates beyond 1.83/2.08 respectively
  7. 7. Upload the firmware file through the router's web interface and wait for installation to complete
  8. 8. After reboot, verify the new firmware version is installed
Caveat Firmware updates may reset router configuration to defaults; backup settings before upgrading and reconfigure after

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Br 6104k Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-4501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data