dbcve.org
Br 6104k Router FirmwareOperating system · Edimax

CVE-2011-4502

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 execute arbitrary commands via shell metacharacters.

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

The UPnP IGD (Internet Gateway Device) implementation in multiple router firmwares contains a command injection vulnerability. Remote attackers can execute arbitrary operating system commands by including shell metacharacters in specially crafted UPnP requests to the affected service.

MitigationDisable UPnP functionality on affected devices if not required, or upgrade firmware to patched versions where available. For unsupported devices, consider network segmentation and blocking external UPnP traffic at the perimeter.

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
    Log into the router web administration interface and locate the device information or status page to confirm the exact model number (e.g., Edimax BR-6104k, Canyon Tech CN-WF512, Edimax 6114wg)
    Affected if The device model matches any of the affected models listed in the CVE (Edimax BR-6104k, Canyon Tech CN-WF512, Canyon Tech CN-WF514, Edimax 6114wg)
  2. Check the installed firmware version
    In the router admin interface, locate the firmware version or software version information (usually under Status, System, or Maintenance sections) and note the exact version number
    Affected if The firmware version matches any of the specific versions listed in the CVE (Edimax 3.21, Canyon Tech 1.83, Canyon Tech 2.08, Edimax 1.83 or 2.08) OR if the device is an affected model running ANY firmware version (since some product entries list 'all versions')
  3. Verify UPnP IGD service status
    In the router admin interface, navigate to the UPnP settings or Port Forwarding settings section and check if UPnP (Universal Plug and Play) or UPnP IGD (Internet Gateway Device) is enabled or turned on
    Affected if UPnP or UPnP IGD functionality is currently enabled on the device
  4. Confirm UPnP service is accessible on the network
    From a computer on the local network, scan the router's internal IP address for open UPnP ports (typically port 1900/UDP for SSDP and TCP ports 49152-49155 for UPnP) or use a UPnP discovery tool to check if the device responds to UPnP discovery requests
    Affected if The router responds to UPnP discovery requests and exposes the IGD service on the network

You are affected if your device is one of the listed models AND UPnP IGD is enabled and accessible, regardless of firmware version for models marked 'all versions' or if your specific firmware version matches the vulnerable versions listed.

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 affected devices if not required, or upgrade firmware to patched versions where available. For unsupported devices, consider network segmentation and blocking external UPnP traffic at the perimeter.

Recommended fix Moderate confidence

Edimax BR-6104K: firmware 3.25 or later; Edimax 6114Wg: latest available firmware; Canyon-Tech CN-WF512: latest available firmware; Canyon-Tech CN-WF514: latest available firmware

  1. 1. Identify the exact model number of the router (BR-6104K, 6114Wg, CN-WF512, CN-WF514, or other affected model).
  2. 2. Visit the official vendor website for your specific router model to download the latest firmware.
  3. 3. For Edimax BR-6104K: Download firmware version 3.25 or later from the Edimax support page.
  4. 4. Access the router's web administration interface (typically at 192.168.1.1 or 192.168.2.1).
  5. 5. Navigate to the Firmware Upgrade or Administration section.
  6. 6. Upload the downloaded firmware file and initiate the upgrade.
  7. 7. Wait for the upgrade to complete and the router to reboot.
  8. 8. After reboot, verify the new firmware version is installed.
Caveat Firmware upgrades on legacy routers may not be available; some routers may require reset to factory defaults after upgrade

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

Fix this in Br 6104k Router Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4502 — 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-4502 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