CVE-2013-0230 is a stack-based buffer overflow (CWE-119) in ExecuteSoapAction() in MiniUPnPd 1.0: a long quoted method name in the SOAPAction header of a UPnP control request overflows a 2,048-byte stack buffer and can run code. NVD scores it 10.0 under CVSS v2. Later MiniUPnPd releases do not have the buffer.
Vulnerability summary
CVSS base score
10
Critical severity
EPSS score (FIRST)
68.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2013-0230 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| MiniUPnPd (MiniUPnP IGD daemon) | cpe:2.3:a:miniupnp_project:miniupnpd:1.0:*:*:*:*:*:*:* | 1.0 (NVD); the 1.1 release no longer copies the method name into a fixed stack buffer |
| OpenWrt packages feed: miniupnpd | cpe: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); none is 1.0 |
What does this mean for affected devices?
NVD's description: "Stack-based buffer overflow in the ExecuteSoapAction function in the SOAPAction handler in the HTTP service in MiniUPnP MiniUPnPd 1.0 allows remote attackers to execute arbitrary code via a long quoted method." NVD's Primary score is CVSS v2 10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C) with CWE-119; the record has no CVSS v3 score. The CPE configuration lists MiniUPnPd 1.0 only, and the references include a public exploit on Exploit-DB. The record was published on 2013-01-31 (NVD).
Where is the overflow?
In the miniupnpd 1.0 tarball on the MiniUPnP download page, ExecuteSoapAction() in upnpsoap.c declares char method[2048], computes the method length as the distance from the # in the SOAPAction value to the next double quote, and, when no known action matches, copies that many bytes into method with memcpy() to log it. Nothing checks the length against the buffer, so a method name longer than 2,048 bytes overwrites the stack. In the 1.1 tarball the function logs the name with syslog(..., "%.*s", methodlen, p) and has no local copy. The SOAP handler is the HTTP side of the daemon, which takes AddPortMapping and the other IGD control actions, and the sample miniupnpd.conf notes that "HTTP is available on all interfaces."
Which devices carried it?
Rapid7's January 2013 report Security Flaws in Universal Plug and Play published the CVE with CVE-2013-0229, the SSDP over-read. It says the MiniUPnP flaws "were fixed over two years ago, yet over 330 products are still using older versions", and its Metasploit scanner flags a device that answers SSDP with miniupnpd/1.0 for both. Rapid7 does not name those products in the blog post, and we found no vendor or CERT advisory that does. Distribution packages are clear of it: OpenWrt's packages feed builds miniupnpd 2.3.11 on master and 2.3.9 on its 24.10 and 25.12 branches as of 2026-11-18, and the Debian security tracker marks Debian's package as not affected. A version-1.0 hit means a vendor SDK that forked MiniUPnPd in early 2008; our MiniUPnPd and UPnP firmware guide covers how to find it in an image.
How do you fix or mitigate it?
Move to a current MiniUPnPd release, which also covers the 2019 fixes for CVE-2019-12107 and CVE-2019-12111. If the vendor daemon cannot be replaced, block the daemon's HTTP port and UDP 1900 on the WAN interface so control requests come only from the LAN. Realtek's miniigd is a separate vendor daemon with its own SOAP flaw, the KEV-listed CVE-2014-8361. The memory corruption fix guide covers bounded copies of request data in device code.
CVE-2013-0230 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.68429, the 99.3rd percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: stack-based buffer overflow in ExecuteSoapAction in the SOAPAction handler in MiniUPnPd 1.0, arbitrary code via a long quoted method; Primary CVSS v2 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C; CWE-119; CPE miniupnpd 1.0; Exploit-DB 36839 tagged Exploit; published 2013-01-31. — NVD
- miniupnpd-1.0.tar.gz upnpsoap.c ExecuteSoapAction(): char method[2048]; methodlen = strchr(p, '"') - p - 1; memcpy(method, p, methodlen) with no length check. miniupnpd-1.1.tar.gz: no local buffer, syslog with %.*s. — MiniUPnP download page
- Rapid7 (2013-01-29): MiniUPnP flaws fixed over two years earlier, over 330 products still on older versions; Metasploit flags miniupnpd/1.0 with CVE-2013-0229 and CVE-2013-0230. — Rapid7
- Sample miniupnpd.conf: 'HTTP is available on all interfaces.' — MiniUPnP project (GitHub)
- OpenWrt packages feed net/miniupnpd/Makefile: 2.3.11 (master), 2.3.9 (openwrt-24.10, openwrt-25.12), read 2026-11-18. — OpenWrt packages
- Debian security tracker: miniupnpd not affected (fixed before initial upload to archive). — Debian security tracker
- CVE-2013-0230 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.68429, percentile 0.99345, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which MiniUPnPd versions are affected by CVE-2013-0230?
NVD lists MiniUPnPd 1.0 only. In the 1.0 source, ExecuteSoapAction() copies the SOAPAction method name into a 2,048-byte stack buffer without a length check; the 1.1 source logs the name without copying it (per NVD and the MiniUPnP release tarballs).
Does an attacker need credentials to exploit CVE-2013-0230?
No. The overflow is in the SOAP handler that receives UPnP control requests over HTTP, before any action runs, which is why NVD scores it 10.0 under CVSS v2. The sample miniupnpd.conf notes that HTTP is available on all interfaces, so firewall the WAN side (per NVD and the MiniUPnP project).
Why does a scanner report CVE-2013-0230 on my router?
Rapid7's Metasploit scanner flags any device whose SSDP reply names miniupnpd/1.0. Current OpenWrt and Debian packages are far newer, so the hit usually means a vendor SDK built on a 2008 MiniUPnPd; check the daemon binary in the firmware image (per Rapid7, OpenWrt and the Debian security tracker).
Is CVE-2013-0230 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.68429, the 99.3rd percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?