Stack-based buffer overflow in the ExecuteSoapAction function in the SOAPAction handler in the HTTP service in MiniUPnP MiniUPnPd 1.0 allow…

published 2013-01-31 13y ago modified 2026-06-16 4mo ago also EUVD-2013-0264

cvss: 10.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 69.2%; EPSS 69.2% chance of exploitation in 30 days, percentile 99.3%
public exploits: 5; Metasploit and Exploit-DB

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.

Is CVE-2013-0230 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2013-01-31 Published
2013-03-27 First public exploit (Metasploit exploit/linux/upnp/miniupnpd_soap_bof)

Exploit prediction

69.15% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

Metasploit exploit/linux/upnp/miniupnpd_soap_bof MiniUPnPd 1.0 Stack Buffer Overflow Remote Code Execution metasploit exploit, normal rank, 2013-03-27
Metasploit auxiliary/scanner/upnp/ssdp_msearch UPnP SSDP M-SEARCH Information Discovery metasploit auxiliary, normal rank
EDB-37517 INFOMARK IMW-C920W MiniUPnPd 1.0 - Denial of Service dos, 2015-07-07
EDB-36839 MiniUPnPd 1.0 (MIPS) - Remote Stack Overflow Remote Code Execution for AirTies RT Series remote, 2015-04-27
EDB-25975 MiniUPnPd 1.0 - Remote Stack Buffer Overflow Remote Code Execution (Metasploit) remote, 2013-06-05

CVSS scores

assigned by	version	score	vector
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

CVE List CVE-2013-0230
NVD CVE-2013-0230

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.