Tg585 Router FirmwareApplication · Technicolor

CVE-2011-4506

HIGH · 7.5 CVSS v2.0 Published 2011-11-22
Fix available
A fix is available. Upgrade to after 7.4 or later.
See remediation →
84/100
Remediation priority · High
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 on the Thomson (aka Technicolor) TG585 with firmware 7.x before 7.4.3.2 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

The UPnP IGD implementation on Thomson/Technicolor TG585 routers with firmware 7.x before 7.4.3.2 allows remote unauthenticated attackers on the WAN to create arbitrary port forwarding mappings by sending a specially crafted SOAP AddPortMapping request. This external forwarding vulnerability permits attackers to map any external port to any internal host, enabling inbound connections to internal network resources.

MitigationUpgrade firmware to version 7.4.3.2 or later, and disable UPnP/IGD service on the WAN interface if not needed.

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
Tg585 Router FirmwareApplication
Affected:<= 7.4
Tg585 RouterHardware / 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
Partial
Integrity
Partial
Availability
Partial

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

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 router model
    Log into the router admin interface (typically 192.168.1.1) and check the device information or status page for the model number. Confirm it is a Thomson or Technicolor TG585 series router.
    Affected if The device is not a TG585 series router - this CVE does not apply.
  2. Check firmware version
    In the router admin interface, look for a firmware or software version field (usually under Status, System, or Administration). Note the exact version number.
    Affected if Firmware version is 7.4.3.2 or higher, or is a version other than 7.x - the specific vulnerability path may differ.
  3. Verify UPnP IGD WAN exposure
    In the router admin interface, navigate to the UPnP or Internet Gateway Device (IGD) settings. Check if UPnP/IGD is enabled and specifically whether it is accessible from the WAN (external) side. Look for options like 'Enable UPnP', 'Allow UPnP from WAN', or 'IGD on WAN interface'.
    Affected if UPnP IGD service is enabled and exposed to the WAN interface - this is the condition that enables the unauthenticated attack.
  4. Test WAN UPnP port accessibility
    From an external network (or using an online port scanner), attempt to connect to the router's public IP on port 5431 (standard UPnP IGD SOAP port). Use a command like 'nc -zv <router_public_ip> 5431' or an external port check service.
    Affected if Port 5431 (or the configured UPnP port) is open and reachable from the WAN - the vulnerability is remotely exploitable.

A TG585 router with firmware 7.x below 7.4.3.2 that has UPnP IGD enabled and exposed on the WAN interface is affected; if UPnP is only enabled on the LAN side, the specific WAN attack vector does not apply.

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.

From vendor data
Upgrade available Upgrade to a release after 7.4
Interim mitigation

Upgrade firmware to version 7.4.3.2 or later, and disable UPnP/IGD service on the WAN interface if not needed.

Fix this in Tg585 Router Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-4506 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