CVE-2012-5965 is a stack-based buffer overflow in the unique_service_name() function of libupnp 1.3.1, the Portable SDK for UPnP Devices, triggered by a long DeviceType field in an SSDP packet to UDP port 1900. NVD scores it 10.0. It belongs to the CERT/CC VU#922681 set, fixed in libupnp 1.6.18, which Cisco and Siemens tied to named devices.
Vulnerability summary
CVSS base score
10
Critical severity
EPSS score (FIRST)
36.9%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2012-5965 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Portable SDK for UPnP Devices (libupnp) 1.3.1 | cpe:2.3:a:portable_sdk_for_upnp_project:portable_sdk_for_upnp:1.3.1:*:*:*:*:*:*:* | 1.3.1 per NVD; CERT/CC lists Portable SDK 1.2.1a to 1.8.0 for the VU#922681 set; fixed in 1.6.18 |
| Cisco TelePresence C Series Endpoints, TelePresence System EX Series, TelePresence SX20 | — | listed as vulnerable in cisco-sa-20130129-upnp revision 1.2 (2013-02-13); no fixed release named in the advisory |
| Siemens OZW772, OZW672, OZW775 and OZS164 building-automation web servers | — | OZW772 firmware before V5.10 and OZW672 before V5.00 (fixed in those versions); OZW775 V3.01 and earlier and OZS164 V2.00 and earlier have no firmware fix, mitigate or migrate (Siemens SSA-963338) |
What does this mean for affected devices?
CVE-2012-5965 is a buffer overflow (CWE-119) in the same SSDP function as CVE-2012-5958, but on a different input. NVD's record says the stack-based overflow in unique_service_name() in ssdp/ssdp_server.c of libupnp 1.3.1 "allows remote attackers to execute arbitrary code via a long DeviceType (aka urn device) field in a UDP packet". NVD scores it 10.0 under CVSS v2, vector AV:N/AC:L/Au:N/C:C/I:C/A:C, a Primary score from NVD itself, and its configuration names only version 1.3.1 (NVD).
Why does a 1.3.1-only CVE matter for firmware today?
Because old SDK lines live on in devices for years. CERT/CC VU#922681, published on 2013-01-29 after Rapid7's scan of Internet-facing UPnP devices, groups CVE-2012-5958 to CVE-2012-5965 and says Portable SDK versions 1.2.1a to 1.8.0 carry at least three remotely exploitable overflows in unique_service_name(), while "versions prior to 1.6.17 are vulnerable to additional issues in the same function". The note traces libupnp to Intel's SDK for UPnP Devices and says that "many different vendors produce UPnP-enabled devices that use libupnp". A device whose UPnP library reports 1.3.x is in the oldest part of that range and should be treated as affected by the whole set, not only by this CVE.
Which vendors named affected devices?
Both vendor advisories list all eight CVE IDs, including this one. Cisco's advisory cisco-sa-20130129-upnp lists TelePresence C Series Endpoints, TelePresence System EX Series and TelePresence SX20 as vulnerable, and says IOS, IOS-XE, IOS-XR, NX-OS and the ASA do not use libupnp. Siemens ProductCERT SSA-963338 names OZW772 firmware before V5.10, OZW672 before V5.00, OZW775 V3.01 and earlier and OZS164 V2.00 and earlier. These are building-automation web servers for heating and air-conditioning controllers. Neither advisory says which of the eight CVEs each product's libupnp version actually contains, so the product names apply to the set as a whole.
Is CVE-2012-5965 exploited?
It is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.3693, the 98.5th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
How do you fix it?
Replace the library: libupnp 1.6.18 fixes the VU#922681 set, and the current pupnp release is the supported line. A 1.3.1 build is far too old to patch one function at a time. Until the firmware is rebuilt, block UDP port 1900 from untrusted networks and switch UPnP off where the product does not need it, as CERT/CC and Siemens advise. Our MiniUPnPd and UPnP vulnerabilities guide shows how to find libupnp and read its version in a firmware image, and our memory corruption guide covers this class of bug. For ranking it next to the rest of the UPnP backlog, see our KEV and EPSS prioritisation guide.
Evidence
- Stack-based overflow in unique_service_name in ssdp/ssdp_server.c, libupnp 1.3.1, long DeviceType (urn device) field; NVD CVSS v2 10.0 Primary; CWE-119; CPE portable_sdk_for_upnp 1.3.1; published 2013-01-31. — NVD
- VU#922681 2013-01-29: 1.2.1a-1.8.0 at least three overflows; versions prior to 1.6.17 additional issues; 1.6.18 fixes; CVE-2012-5958 to CVE-2012-5965. — CERT/CC VU#922681
- Lists CVE-2012-5958 to CVE-2012-5965; vulnerable TelePresence C, EX, SX20; IOS, IOS-XE, IOS-XR, NX-OS, ASA, FWSM not affected. — Cisco cisco-sa-20130129-upnp
- Related CVEs CVE-2012-5958 to CVE-2012-5965; OZW772 < V5.10, OZW672 < V5.00, OZW775 <= V3.01, OZS164 <= V2.00. — Siemens SSA-963338
- Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.36925 (98.54th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
How is CVE-2012-5965 different from CVE-2012-5958?
Both are stack overflows in libupnp's unique_service_name() SSDP function. CVE-2012-5965 is triggered by a long DeviceType field and NVD lists only libupnp 1.3.1, while CVE-2012-5958 covers releases through 1.6.17 (per NVD).
Which libupnp version fixes CVE-2012-5965?
CERT/CC says libupnp 1.6.18 fixes the overflows in the VU#922681 set, which includes CVE-2012-5965 (per CERT/CC VU#922681).
Which products did vendors list for this CVE set?
Cisco lists TelePresence C Series, EX Series and SX20 as vulnerable, and Siemens names OZW772, OZW672, OZW775 and OZS164 building-automation web servers. Both advisories list all eight CVEs from CVE-2012-5958 to CVE-2012-5965 (per Cisco cisco-sa-20130129-upnp and Siemens SSA-963338).
Is CVE-2012-5965 known to be exploited?
It is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.3693, the 98.5th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?