Insufficient access protection in firmware in Intel Server Board, Intel Server System and Intel Compute Module before firmware version 00.01
Insufficient access protection in firmware in Intel Server Board, Intel Server System and Intel Compute Module before firmware version 00.01.0014 may allow an unauthenticated attacker to potentially execute arbitrary code resulting in information disclosure, escalation of privilege and/or denial of service via local access.
- Published
- Oct 10, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-732
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| intel | server board s2600bp firmware | cpe:2.3:o:intel:server_board_s2600bp_firmware |
| intel | server board s2600bp | cpe:2.3:h:intel:server_board_s2600bp |
| intel | server board s2600wf firmware | cpe:2.3:o:intel:server_board_s2600wf_firmware |
| intel | server board s2600wf | cpe:2.3:h:intel:server_board_s2600wf |
| intel | server board s2600st firmware | cpe:2.3:o:intel:server_board_s2600st_firmware |
| intel | server board s2600st | cpe:2.3:h:intel:server_board_s2600st |
| intel | server board s2600bpr firmware | cpe:2.3:o:intel:server_board_s2600bpr_firmware |
| intel | server board s2600bpr | cpe:2.3:h:intel:server_board_s2600bpr |
| intel | server board s2600wfr firmware | cpe:2.3:o:intel:server_board_s2600wfr_firmware |
| intel | server board s2600wfr | cpe:2.3:h:intel:server_board_s2600wfr |
| intel | server board s2600str firmware | cpe:2.3:o:intel:server_board_s2600str_firmware |
| intel | server board s2600str | cpe:2.3:h:intel:server_board_s2600str |
and 16 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel compute module hns2600bp firmwarebefore 00.01.0014
- intel compute module hns2600bpr firmwarebefore 00.01.0014
- intel server board s2600bp firmwarebefore 00.01.0014
- intel server board s2600bpr firmwarebefore 00.01.0014
- intel server board s2600st firmwarebefore 00.01.0014
- intel server board s2600str firmwarebefore 00.01.0014
- intel server board s2600wf firmwarebefore 00.01.0014
- intel server board s2600wfr firmwarebefore 00.01.0014
- intel server system h2000g firmwarebefore 00.01.0014
- intel server system h2000gr firmwarebefore 00.01.0014
- intel server system r1000wf firmwarebefore 00.01.0014
- intel server system r1000wfr firmwarebefore 00.01.0014
- intel server system r2000wf firmwarebefore 00.01.0014
- intel server system r2000wfr firmwarebefore 00.01.0014
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
Intel Corporation Intel Server Boards Firmware
- before 00.01.0014affected
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-primary
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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- support.lenovo.com/us/en/solutions/LEN-24799
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00179.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.