CVE-2008-4722
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 Sun Integrated Lights-Out Manager (ILOM) 2.0.1.5 through 2.0.4.26 allows remote authenticated users to (1) access the service processor (SP) and cause a denial of service (shutdown or reboot), or (2) access the host operating system and have an unspecified impact, 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 · moderate confidenceUnspecified vulnerability in Sun Integrated Lights-Out Manager (ILOM) versions 2.0.1.5 through 2.0.4.26 allows remote authenticated users to access the service processor causing denial of service via shutdown/reboot, or to access the host operating system with unspecified impact. The CVSS score of 9 indicates critical severity due to remote authenticated attack vector and high availability impact.
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 versions<= 2.0<= 2.0<= 2.1.1<= 2.1.1<= 7.1.6<= 2.0<= 2.0CVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/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 if Sun ILOM is presentAccess the service processor web interface, or use IPMI commands (ipmitool -I lanplus -H <ILOM_IP> -U <user> selftest) to confirm ILOM is running. On Sun Blade hardware, ILOM is typically the default service processor firmware.Affected if The system has Sun ILOM service processor firmware installed.
-
Retrieve the ILOM firmware versionLog into the ILOM CLI via SSH or serial console and run the 'show /SP/firmware' command, or check the web interface System Information page for the firmware build number.Affected if Unable to retrieve version information from the service processor.
-
Compare version against vulnerable rangeCompare the installed ILOM firmware version to the affected range: 2.0.1.5 through 2.0.4.26. Note that versions prior to 2.0.1.5 and versions after 2.0.4.26 are not listed as vulnerable in this CVE.Affected if The installed version falls within 2.0.1.5 to 2.0.4.26 inclusive.
-
Verify remote management access is enabledCheck ILOM network configuration via 'show /SP/network' in the ILOM CLI or the web interface. Confirm the management network interface is enabled and reachable from the network.Affected if Remote network access to ILOM is enabled and the service processor is network-reachable.
-
Confirm authentication is possibleVerify that ILOM user accounts exist and remote authentication (LDAP, RADIUS, or local user accounts) is configured. The vulnerability requires an authenticated attacker.Affected if Remote authentication is configured and functional for ILOM access.
The environment is affected if Sun ILOM firmware version is 2.0.1.5 through 2.0.4.26 and ILOM is network-accessible to authenticated users.
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.
dbcve · scopedApply vendor-supplied ILOM firmware patches to upgrade beyond version 2.0.4.26. Restrict network access to ILOM management interfaces using firewall rules or network segmentation to limit exposure to authenticated attackers until patching is completed.
ILOM version greater than 2.0.4.26 (contact Oracle for exact fixed release)
- 1. Identify the current ILOM version by accessing the ILOM web interface or via CLI using 'version' command
- 2. Confirm the ILOM version falls within the affected range: 2.0.1.5 through 2.0.4.26
- 3. Contact Oracle Support or consult Oracle ILOM documentation to obtain the appropriate firmware version that addresses CVE-2008-4722
- 4. Download the patched ILOM firmware from Oracle's official support channels
- 5. Follow Oracle's documented firmware update procedure for your specific Sun Blade hardware platform
- 6. Verify the upgrade was successful by confirming the new ILOM version is beyond 2.0.4.26
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-4722 — 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-2008-4722 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