dbcve.org
Portable Sdk For UpnpApplication · Portable Sdk For Upnp Project

CVE-2012-5963

HIGH · 10.0 CVSS v2.0 Published 2013-01-31
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable SDK for UPnP Devices (aka libupnp, formerly the Intel SDK for UPnP devices) 1.3.1 allows remote attackers to execute arbitrary code via a long UDN (aka uuid) field within a string that lacks a :: (colon colon) in a UDP packet.

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

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in libupnp 1.3.1 allows remote attackers to execute arbitrary code via a long UDN (UUID) field within a UDP packet that lacks the required :: (colon colon) delimiter.

MitigationUpgrade libupnp to version 1.3.2 or later which contains the fix for proper UDN field length validation, or apply vendor-supplied patches to the vulnerable function.

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
Portable Sdk For UpnpApplication
Affected:= 1.3.1

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 installed libupnp version
    Check for libupnp library files or binary version info. On Linux: dpkg -l | grep libupnp, rpm -qa | grep upnp, or check /usr/lib/libupnp* files. On Windows: check Program Files for UPnP-related software or examine the DLL version property.
    Affected if The installed version is libupnp 1.3.1 exactly, or if version cannot be determined but the library dates to the 1.3.x era before 1.3.2.
  2. Locate the vulnerable ssdp_server.c source file
    Search the system for the file ssdp/ssdp_server.c or the compiled ssdp_server.o object file. Common paths include /path/to/libupnp/ or within source code directories of applications that embed libupnp.
    Affected if The file exists and, when examined, contains the unique_service_name function with no length validation on the UDN parameter.
  3. Verify SSDP/UPnP functionality is enabled
    Check running processes for upnp or ssdp daemons (ps aux | grep -i upnp). On Linux systems, check /etc/igd.conf or similar UPnP configuration files. For applications using libupnp, check their configuration for UPnP/SSDP discovery features.
    Affected if SSDP server or UPnP control point functionality is actively running or configured to start, creating a network attack surface.
  4. Confirm network exposure to SSDP UDP traffic
    Check firewall rules or network configuration for UDP port 1900 (SSDP multicast) exposure. Use netstat -anu | grep 1900 or similar to see if the system is listening on this port.
    Affected if The system listens on UDP port 1900 or accepts SSDP/UPnP discovery packets from untrusted networks, allowing remote attackers to send malicious UDP packets.

A system is affected if it runs libupnp version 1.3.1 with SSDP/UPnP functionality enabled and exposed to network traffic, allowing a remote attacker to send a crafted UDP packet with an overlength UDN field lacking the :: delimiter to trigger the buffer overflow.

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
Patch available Apply the vendor patch
Vendor patch www.kb.cert.org →
Interim mitigation

Upgrade libupnp to version 1.3.2 or later which contains the fix for proper UDN field length validation, or apply vendor-supplied patches to the vulnerable function.

Recommended fix High confidence

libupnp 1.6.x or later (1.8.x recommended)

  1. 1. Identify all systems and applications using libupnp (portable SDK for UPnP devices) version 1.3.1
  2. 2. Download the latest stable release of libupnp from the official source (https://sourceforge.net/projects/pupnp/)
  3. 3. Extract the new version archive
  4. 4. Navigate to the extracted directory: cd libupnp-[version]
  5. 5. Run the configure script: ./configure
  6. 6. Compile the library: make
  7. 7. Install the updated library: make install
  8. 8. Update any dependent applications to link against the new library version
Caveat Minor: recompilation of dependent applications may be required; verify any custom code using the UPnP API functions remains compatible

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

Fix this in Portable Sdk For Upnp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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