CVE-2013-3607
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple stack-based buffer overflows in the web interface in the Intelligent Platform Management Interface (IPMI) implementation on Supermicro H8DC*, H8DG*, H8SCM-F, H8SGL-F, H8SM*, X7SP*, X8DT*, X8SI*, X9DAX-*, X9DB*, X9DR*, X9QR*, X9SBAA-F, X9SC*, X9SPU-F, and X9SR* devices allow remote attackers to execute arbitrary code on the Baseboard Management Controller (BMC), as demonstrated by the (1) username or (2) password field in login.cgi.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple stack-based buffer overflows in the IPMI web interface (login.cgi) on Supermicro Baseboard Management Controllers allow remote attackers to execute arbitrary code by overflowing the username or password fields with excessive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the BMC modelAccess the IPMI web interface or use IPMI commands (ipmitool -I lanplus -H <IPMI_IP> -u ADMIN -P ADMIN chassis status) to retrieve the BMC product name and model numberAffected if The model matches one of: H8dcl-6f, H8dcl-If, H8dclt-Hibqf, H8dclt-Hln4f, H8dclt-Ibqf, H8dgg6-F, H8dgg-Qf, H8dgi-F (or variants with similar H8dcl/H8dct/H8dgg/H8dgi designations)
-
Verify IPMI web interface is enabledAttempt to access the login.cgi page via HTTP/HTTPS (e.g., https://<IPMI_IP>/cgi/login.cgi) or check BMC network settings for web interface statusAffected if The web interface (login.cgi) responds and accepts authentication input
-
Check BMC firmware versionUse IPMI command: ipmitool -I lanplus -H <IPMI_IP> -u ADMIN -P ADMIN mc info or access BMC web UI firmware info pageAffected if Any firmware version is installed on an affected model (all versions of these models are vulnerable)
-
Confirm IPMI network accessibilityTest TCP port 80/443 connectivity to the IPMI interface IP address from an external hostAffected if The IPMI web interface is reachable over the network (indicating potential remote exploitation vector)
You are affected if you have a Supermicro BMC from the H8dcl, H8dct, H8dgg, or H8dgi series with the IPMI web interface enabled and accessible, regardless of firmware version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate BMC firmware to vendor-patched version; if patches unavailable, restrict network access to IPMI interfaces or disable the web interface until firmware is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-3607 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data