Multiple stack-based buffer overflows in cgi/close_window.cgi in the web interface in the Intelligent Platform Management Interface (IPMI)…

published 2013-12-10 12y ago modified 2026-06-16 4mo ago also EUVD-2013-3557

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

Multiple stack-based buffer overflows in cgi/close_window.cgi in the web interface in the Intelligent Platform Management Interface (IPMI) with firmware before 3.15 (SMT_X9_315) on Supermicro X9 generation motherboards allow remote attackers to execute arbitrary code via the (1) sess_sid or (2) ACT parameter.

Is CVE-2013-3623 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-11-06 First public exploit (Metasploit auxiliary/scanner/http/smt_ipmi_cgi_scanner)
2013-12-10 Published

Exploit prediction

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

Exploits and checks

Metasploit auxiliary/scanner/http/smt_ipmi_cgi_scanner Supermicro Onboard IPMI CGI Vulnerability Scanner metasploit auxiliary, normal rank, 2013-11-06
Metasploit exploit/linux/http/smt_ipmi_close_window_bof Supermicro Onboard IPMI close_window.cgi Buffer Overflow metasploit exploit, good rank, 2013-11-06
EDB-29666 Supermicro Onboard IPMI - 'close_window.cgi' Remote Buffer Overflow (Metasploit) remote, 2013-11-18
community.rapid7.com https://community.rapid7.com/community/metasploit/blog/2013/11/06/supermicro-ipmi-firmware-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified

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-3623
NVD CVE-2013-3623

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.