dbcve.org
Server Board M70klp2sb FirmwareOperating system · Intel

CVE-2022-29262

MEDIUM · 6.7 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 01.04.0022 / 02.01.0015 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click Patch available

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 · unedited
Improper buffer restrictions in some Intel(R) Server Board BIOS firmware may allow a privileged user to potentially enable escalation of privilege 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

A detailed technical summary for this CVE is being prepared.

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
Server Board M70klp2sb FirmwareOperating system
Affected:< 01.04.0022
Server System M70klp4s2uhh FirmwareOperating system
Affected:< 01.04.0022
Server Board M20ntp2sb FirmwareOperating system
Affected:< 0022.d02
Server System M20ntp1ur304 FirmwareOperating system
Affected:< 0022.d02
Server Board M10jnp2sb FirmwareOperating system
Affected:< 7.219
Server Board S2600bpbr FirmwareOperating system
Affected:< 02.01.0015
Server Board S2600bps FirmwareOperating system
Affected:< 02.01.0015
Server Board S2600bpsr FirmwareOperating system
Affected:< 02.01.0015

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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 01.04.0022 / 02.01.0015 / 7.219 or later
Fixed in 01.04.002202.01.00157.219
Vendor patch www.intel.com →
Recommended fix High confidence

Firmware version 01.04.0022 for M70klp2sb/M70klp4s2uhh, 0022.d02 for M20ntp2sb/M20ntp1ur304, 7.219 for M10jnp2sb, or 02.01.0015 for S2600bpbr/S2600bps/S2600bpsr

  1. 1. Identify the exact server board or system model from the affected product list (M70klp2sb, M70klp4s2uhh, M20ntp2sb, M20ntp1ur304, M10jnp2sb, S2600bpbr, S2600bps, or S2600bpsr)
  2. 2. Download the latest BIOS/firmware version from Intel's support site or the Intel Security Advisory INTEL-SA-00719
  3. 3. For the identified product, obtain firmware version 01.04.0022 (M70klp2sb/M70klp4s2uhh), 0022.d02 (M20ntp2sb/M20ntp1ur304), 7.219 (M10jnp2sb), or 02.01.0015 (S2600bpbr/S2600bps/S2600bpsr)
  4. 4. Follow Intel's standard BIOS/firmware update procedure, typically involving running the firmware update utility from a USB bootable environment or via Intel's Integrated BMC Web Console
  5. 5. Ensure the system is powered on and connected to stable power during the firmware update process
  6. 6. After update completes, verify the BIOS version matches the fixed release
Caveat BIOS firmware updates carry risk of system boot failure if interrupted; ensure stable power and follow Intel's update instructions precisely

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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