Security Advisory

CVE-2013-0229: MiniUPnPd SSDP Request Over-Read

Last updated:
  • CVE-2013-0229

CVE-2013-0229 is a buffer over-read in ProcessSSDPRequest(), the SSDP handler of the MiniUPnPd UPnP IGD daemon, in versions before 1.4: one crafted M-SEARCH datagram to UDP port 1900 crashes the daemon. NVD scores it 7.8 under CVSS v2. MiniUPnPd 1.4, released in 2009, fixes it.

Vulnerability summary

CVSS base score

7.8

High severity

EPSS score (FIRST)

75.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2013-0229 · Source: NVD

Affected components

ComponentCPEVersion range
MiniUPnPd (MiniUPnP IGD daemon)cpe:2.3:a:miniupnp_project:miniupnpd:*:*:*:*:*:*:*:*1.0 to 1.3 (NVD: through 1.3); fixed in 1.4, released 2009-10-30
OpenWrt packages feed: miniupnpdcpe:2.3:a:miniupnp_project:miniupnpd:*:*:*:*:*:*:*:*2.1 on openwrt-18.06, 2.3.9 on openwrt-24.10 and openwrt-25.12, 2.3.11 on master (read 2026-11-18); all after 1.4

What does this mean for affected devices?

NVD's description: "The ProcessSSDPRequest function in minissdp.c in the SSDP handler in MiniUPnP MiniUPnPd before 1.4 allows remote attackers to cause a denial of service (service crash) via a crafted request that triggers a buffer over-read." NVD's Primary score is CVSS v2 7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C); the record has no CVSS v3 score and no CWE (NVD-CWE-noinfo). Its CPE configuration marks MiniUPnPd through 1.3 as vulnerable. The record was published on 2013-01-31 (NVD).

What did MiniUPnPd 1.4 change?

The project's Changelog has the entry "Fixed a buffer overflow in ProcessSSDPRequest()" dated 2009/05/16, and "VERSION 1.4 : released the 2009/10/30". Comparing the 1.3 and 1.4 release tarballs from the MiniUPnP download page shows the change: the loop that walks the datagram looking for CRLF line ends and an ST: header gained i < n - 1 and i < n - 3 bounds on the received length n, and the reply is only built when the ST value is not empty. In 1.3, a datagram without the expected line ends lets the scan run past the bytes that were received.

Why does a 2009 fix carry a 2013 CVE?

Rapid7's HD Moore published the CVE in the January 2013 report Security Flaws in Universal Plug and Play. It found more than 80 million unique IPs answering UPnP discovery from the Internet and says "the flaws identified in the MiniUPnP software were fixed over two years ago, yet over 330 products are still using older versions." Rapid7's Metasploit scanner flags a device that answers SSDP with miniupnpd/1.0 for both this CVE and CVE-2013-0230, the SOAPAction stack overflow in the same release. The version in that SERVER string is the quickest check on a device; our MiniUPnPd and UPnP firmware guide shows where to find it in an unpacked image.

Current build systems carry much newer code. On 2026-11-18 the OpenWrt packages feed builds miniupnpd 2.3.11 on master and 2.3.9 on openwrt-24.10 and openwrt-25.12, and openwrt-18.06 packaged 2.1. The Debian security tracker marks its miniupnpd package as not affected, fixed before the first upload. A hit on this CVE therefore points to a vendor SDK that froze a 2008-era MiniUPnPd, not to a current distribution package.

How do you fix or mitigate it?

Replace the daemon with a current MiniUPnPd release, not a 1.4 build: the later 2.1 line still had the heap information leak CVE-2019-12107 and the PCP NULL dereference CVE-2019-12111. Keep SSDP on the LAN side: the sample miniupnpd.conf binds SSDP to the interfaces named in listening_ip and notes that "HTTP is available on all interfaces", so the WAN firewall must drop UDP 1900 and the daemon's HTTP port. The libupnp SSDP overflow CVE-2012-5958 from the same 2013 research shows the other common stack, and the memory corruption fix guide covers bounds checks of this kind in device code.

CVE-2013-0229 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.75861, the 99.5th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: ProcessSSDPRequest in minissdp.c in MiniUPnPd before 1.4, buffer over-read, DoS; Primary CVSS v2 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C; no v3 score; NVD-CWE-noinfo; CPE miniupnpd through 1.3 (plus 1.0, 1.1, 1.2); published 2013-01-31. — NVD
  • MiniUPnPd Changelog: 2009/05/16 'Fixed a buffer overflow in ProcessSSDPRequest()'; 'VERSION 1.4 : released the 2009/10/30'. — MiniUPnP project (GitHub)
  • miniupnpd-1.3.tar.gz vs miniupnpd-1.4.tar.gz, minissdp.c ProcessSSDPRequest(): 1.4 adds (i < n - 1) and (i < n - 3) bounds to the CRLF/ST: scan and requires st_len > 0. — MiniUPnP download page
  • Rapid7 (HD Moore, 2013-01-29): over 80 million unique IPs responded to UPnP discovery; MiniUPnP flaws fixed over two years earlier, over 330 products still on older versions; Metasploit ssdp_msearch flags miniupnpd/1.0 with CVE-2013-0229 and CVE-2013-0230. — Rapid7
  • OpenWrt packages feed net/miniupnpd/Makefile: PKG_VERSION 2.3.11 (master), 2.3.9 (openwrt-24.10, openwrt-25.12), 2.1 (openwrt-18.06), read 2026-11-18. — OpenWrt packages
  • Debian security tracker: miniupnpd not affected (fixed before initial upload to archive). — Debian security tracker
  • Sample miniupnpd.conf: listening_ip lines select SSDP interfaces; 'HTTP is available on all interfaces.' — MiniUPnP project (GitHub)
  • CVE-2013-0229 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.75861, percentile 0.99533, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. MiniUPnPd Changelog
  3. MiniUPnP project: release downloads
  4. Rapid7: Security Flaws in Universal Plug and Play (2013)
  5. OpenWrt packages: miniupnpd Makefile
  6. Debian security tracker
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Which MiniUPnPd versions are affected by CVE-2013-0229?

NVD lists MiniUPnPd 1.0 through 1.3. The project's Changelog records the ProcessSSDPRequest() fix on 2009/05/16, and MiniUPnPd 1.4, released on 2009/10/30, is the first release with it (per NVD and the MiniUPnPd Changelog).

How can I tell from the network whether a device runs an affected MiniUPnPd?

MiniUPnPd puts its version in the SERVER string of SSDP replies. Rapid7's Metasploit scanner flags a device that answers with miniupnpd/1.0 for CVE-2013-0229 and CVE-2013-0230. A vendor can change that string, so confirm against the firmware image (per Rapid7).

Can CVE-2013-0229 be reached from the Internet?

Only where the device answers SSDP on its WAN side. Rapid7 found more than 80 million IPs that responded to UPnP discovery from the Internet in 2012. Bind SSDP to LAN interfaces with listening_ip and drop UDP 1900 at the WAN firewall (per Rapid7 and the sample miniupnpd.conf).

Is CVE-2013-0229 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.75861, the 99.5th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).