dbcve.org
Compute Module Hns2600bp FirmwareOperating system · Intel

CVE-2022-29510

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

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 M10JNP2SB BIOS firmware before version 7.219 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 · moderate confidence

Improper buffer restrictions in Intel Server Board M10JNP2SB BIOS firmware before version 7.219 allows a privileged local user to escalate privileges. This is a buffer overflow vulnerability in the BIOS that can be exploited by an already-privileged attacker with local access to the system.

MitigationUpdate BIOS firmware to version 7.219 or later. Since this requires local access by a privileged user, ensure physical and console access controls are enforced until the patch is applied.

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 data
Compute Module Hns2600bp FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpb FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpb24 FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpb24r FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpblc FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpblc24 FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpblc24r FirmwareOperating system
Affected:< 02.01.0015
Compute Module Hns2600bpblcr 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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Intel Compute Module model
    Check the server chassis, system documentation, or use dmidecode -s system-product-name to determine if the system is an Hns2600bp, Hns2600bpb, Hns2600bpb24, Hns2600bpb24r, Hns2600bpblc, Hns2600bpblc24, Hns2600bpblc24r, or Hns2600bpblcr model
    Affected if The system is any of these eight Intel Compute Module variants
  2. Check the installed BIOS firmware version
    Access the BMC/IPMI web interface or use ipmitool raw commands (e.g., ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw ... ) to retrieve the BIOS firmware version; alternatively, boot into BIOS setup and check the BIOS version displayed on the main screen
    Affected if The displayed BIOS firmware version is below 02.01.0015
  3. Verify the firmware version format
    Confirm the version number format matches the Intel versioning scheme (e.g., 02.01.0014, 02.01.0015, etc.); ensure you are reading the BIOS/UEFI firmware version, not the BMC firmware version
    Affected if The firmware version cannot be determined or is reported in a different format that prevents comparison to 02.01.0015

A user is affected if they have an Intel Compute Module Hns2600bp family system with BIOS firmware version earlier than 02.01.0015.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 02.01.0015 or later
Fixed in 02.01.0015
Interim mitigation

Update BIOS firmware to version 7.219 or later. Since this requires local access by a privileged user, ensure physical and console access controls are enforced until the patch is applied.

Recommended fix High confidence

Intel Compute Module HNS2600BP family firmware version 02.01.0015

  1. 1. Identify the specific Intel Compute Module model from the Hns2600bp* family (e.g., Hns2600bp, Hns2600bpb, Hns2600bpb24, Hns2600bpblc, etc.) in your environment.
  2. 2. Download the latest Intel Compute Module HNS2600BP family firmware version 02.01.0015 or later from Intel's support website at www.intel.com.
  3. 3. Update the BMC (Baseboard Management Controller) firmware first, following Intel's standard BMC firmware update procedure for your compute module.
  4. 4. Then update the BIOS firmware to version 02.01.0015 or later using Intel's recommended firmware update tool or BMC web interface.
  5. 5. After the update completes, verify the installed firmware version matches 02.01.0015 or later to confirm the remediation.
Caveat Firmware updates carry inherent risk; ensure power stability during the update process and back up critical configuration data before proceeding

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

Fix this in Compute Module Hns2600bp Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29510 — 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-29510 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