CVE-2023-22662
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 · uneditedImproper input validation of EpsdSrMgmtConfig in UEFI firmware for some Intel(R) Server Board S2600BP products may allow a privileged user to potentially enable denial of service via local access.
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 confidenceImproper input validation in the EpsdSrMgmtConfig parameter within UEFI firmware for Intel Server Board S2600BP allows a privileged local user to trigger a denial of service condition by providing malformed input to this configuration setting.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:H
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.
-
Verify the system model is an affected Intel Server BoardCheck the server or system documentation, BIOS setup, or use commands like `dmidecode -s system-product-name` or IPMI to confirm the exact system model is Intel Server Board S2600BPAffected if The system model is not Intel Server Board S2600BP (other models are not affected by this specific CVE)
-
Identify the installed UEFI firmware versionAccess the UEFI/BIOS setup screen during boot, or retrieve via IPMI: `ipmitool raw` command, or check via BMC web interface under Firmware Inventory. The version typically appears as a build number like XX.XX.XX.XXXXAffected if The installed firmware version cannot be determined or is not from Intel's S2600BP firmware line
-
Compare installed firmware version to Intel's fixed versionObtain the Intel advisory for CVE-2023-22662 (refer to Intel Security Bulletin INTEL-SA-00997) and compare your installed firmware build number against the fixed version listed for S2600BPAffected if The installed firmware version is older than the fixed version Intel has published for this vulnerability
-
Confirm access to EpsdSrMgmtConfig parameter is possibleThis parameter is a UEFI firmware configuration setting accessible through the BIOS setup utility or via IPMI/BMC remote management interfaces. Verify if your role permits access to this configurationAffected if A privileged local user account exists that can access and modify UEFI configuration settings including EpsdSrMgmtConfig
You are affected if your system is an Intel Server Board S2600BP running firmware older than the version Intel has designated as fixed for this input validation vulnerability in the EpsdSrMgmtConfig parameter.
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 dataApply the Intel firmware update for affected S2600BP products. As this is a firmware-level vulnerability, no configuration change can mitigate it; patching is required.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22662 — 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-2023-22662 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