CVE-2013-4843
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 · uneditedUnspecified vulnerability in HP Integrated Lights-Out 4 (iLO4) with firmware before 1.32 allows remote authenticated users to obtain sensitive information via unknown vectors.
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 confidenceHP Integrated Lights-Out 4 (iLO4) firmware versions prior to 1.32 contain an unspecified vulnerability allowing authenticated remote users to obtain sensitive information. The attack requires valid credentials, suggesting the vulnerability may involve improper access controls or information exposure in specific iLO functions.
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 data<= 1.27a= 1.10= 1.15= 1.15a= 1.16a= 1.20a= 1.26aall 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
- Single
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:S/C:C/I:N/A:N
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 iLO4 firmware version via web interfaceLog in to the iLO4 web interface and navigate to the 'Overview' or 'Information' page under 'Integrated Lights-Out 4'. The firmware version is displayed in the 'Firmware Version' or 'iLO Firmware' field.Affected if The displayed firmware version is any version prior to 1.32 (for example, 1.30, 1.31, 1.27a, 1.20a) or if the version cannot be determined but iLO4 is present.
-
Identify iLO4 firmware version via SSHConnect to the iLO4 IP address using SSH (for example, using Putty or ssh command). Log in with administrative credentials. At the CLI prompt, type 'info' or 'show /map1/firmware1' to retrieve firmware version information.Affected if The reported firmware version is below 1.32.
-
Identify iLO4 firmware version from host operating systemOn the managed server OS, use HP management tools such as 'hpasmcli' (HP Array Configuration Utility) and run 'show iml' or 'show server'. Alternatively, use 'hponcfg' (HP Online Configuration) to query iLO: 'hponcfg -g' or check the iLO event log. The firmware version appears in the output.Affected if The reported iLO firmware version is less than 1.32.
-
Confirm iLO4 generationVerify that the affected device is specifically iLO4 (not iLO 2 or iLO 3). In the iLO web interface, the product name is displayed on the login page or in the 'Overview' section. In CLI, 'help system' or 'show /map1' displays the product identifier.Affected if The device is confirmed as iLO4 and the firmware version is below 1.32.
A system is affected if it is running HP Integrated Lights-Out 4 (iLO4) firmware with any version prior to 1.32, because all iLO4 versions before that update contain the information disclosure vulnerability.
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 iLO4 firmware to version 1.32 or later to remediate this vulnerability. Ensure strong credential management for iLO interfaces as an additional control.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4843 — 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-4843 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