Unspecified vulnerability in Sun Integrated Lights-Out Manager (ILOM) 2.0.1.5 through 2.0.4.26 allows remote authenticated users to (1) acce
Unspecified 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.
- Published
- Oct 23, 2008
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 80th percentile
- CWE
- CWE-287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| sun | integrated lights-out manager | cpe:2.3:a:sun:integrated_lights-out_manager |
| sun | blade 6000 modular system with chassis | cpe:2.3:h:sun:blade_6000_modular_system_with_chassis |
| sun | blade 6048 modular system with chassis | cpe:2.3:h:sun:blade_6048_modular_system_with_chassis |
| sun | blade 8000 modular system | cpe:2.3:h:sun:blade_8000_modular_system |
| sun | blade 8000p modular system | cpe:2.3:h:sun:blade_8000p_modular_system |
| sun | blade t6320 server module | cpe:2.3:h:sun:blade_t6320_server_module |
| sun | blade x6220 with server module software | cpe:2.3:h:sun:blade_x6220_with_server_module_software |
| sun | blade x6250 with server module software | cpe:2.3:h:sun:blade_x6250_with_server_module_software |
| sun | blade x6450 with server module software | cpe:2.3:h:sun:blade_x6450_with_server_module_software |
| sun | blade x8400 | cpe:2.3:h:sun:blade_x8400 |
| sun | blade x8420 | cpe:2.3:h:sun:blade_x8420 |
| sun | blade x8440 | cpe:2.3:h:sun:blade_x8440 |
and 25 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sun blade 6000 modular system with chassisup to 2.0 inclusive
- sun blade 6048 modular system with chassisup to 2.0 inclusive
- sun blade 8000 modular systemup to 2.1.1 inclusive
- sun blade 8000p modular systemup to 2.1.1 inclusive
- sun blade t6320 server moduleup to 7.1.6 inclusive
- sun blade x6220 with server module softwareup to 2.0 inclusive
- sun blade x6250 with server module softwareup to 2.0 inclusive
- sun blade x6450 with server module softwareup to 2.0 inclusive
- sun blade x8400up to 2.0.2 inclusive
- sun blade x8420up to 2.0.2 inclusive
- sun blade x8440up to 2.0.2 inclusive
- sun blade x8450up to 2.1 inclusive
- sun fire x2250 serverup to sw_1.1 inclusive
- sun fire x4100 serverup to sw_1.5.1 inclusive
- sun fire x4100m2 serverup to sw_2.1 inclusive
- sun fire x4140 serverup to sw_2.1 inclusive
- sun fire x4150 serverup to sw_2.0 inclusive
- sun fire x4200 serverup to sw_1.5.1 inclusive
- sun fire x4200m2 serverup to sw_2.1 inclusive
- sun fire x4240 serverup to sw_2.1 inclusive
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:L/Au:S/C:C/I:C/A:C
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- secunia.com/advisories/32298
- sunsolve.sun.com/search/document.do?assetkey=1-26-243486-1
- www.securityfocus.com/bid/31861
- www.securitytracker.com/id?1021094
- www.vupen.com/english/advisories/2008/2890
- exchange.xforce.ibmcloud.com/vulnerabilities/46023
Vendor advisories and official records. Exploit/PoC links are deliberately left out.