dbcve.org
Esprimo D556\/2 FirmwareOperating system · Fujitsu

CVE-2023-40238

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-07
Fix available
A fix is available. Upgrade to 1.31.0 / 1.35.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Public exploit 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
A LogoFAIL issue was discovered in BmpDecoderDxe in Insyde InsydeH2O with kernel 5.2 before 05.28.47, 5.3 before 05.37.47, 5.4 before 05.45.47, 5.5 before 05.53.47, and 5.6 before 05.60.47 for certain Lenovo devices. Image parsing of crafted BMP logo files can copy data to a specific address during the DXE phase of UEFI execution. This occurs because of an integer signedness error involving PixelHeight and PixelWidth during RLE4/RLE8 compression.

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
Esprimo D556\/2 FirmwareOperating system
Affected:< 1.35.0
Esprimo D6011 FirmwareOperating system
Affected:< 1.31.0
Esprimo D6012 FirmwareOperating system
Affected:< 3.08.0
Esprimo D7010 FirmwareOperating system
Affected:< 1.64.0
Esprimo D7010\/8 FirmwareOperating system
Affected:< 1.64.0
Esprimo D7011 FirmwareOperating system
Affected:< 1.31.0
Esprimo D7012 FirmwareOperating system
Affected:< 3.08.0
Esprimo D7013 FirmwareOperating system
Affected:< 3.08.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 1.31.0 / 1.35.0 / 1.64.0 or later
Fixed in 1.31.01.35.01.64.0
Recommended fix Moderate confidence

Esprimo D556/2: firmware 1.35.0 or later | Esprimo D6011: firmware 1.31.0 or later | Esprimo D6012: firmware 3.08.0 or later | Esprimo D7010: firmware 1.64.0 or later | Esprimo D7010/8: firmware 1.64.0 or later | Esprimo D7011: firmware 1.31.0 or later | Esprimo D7012: firmware 3.08.0 or later | Esp

  1. 1. Identify the exact Esprimo model from the affected list: D556/2, D6011, D6012, D7010, D7010/8, D7011, D7012, or D7013
  2. 2. Determine the current firmware version installed on the device (typically accessible via BIOS setup or system information utility)
  3. 3. Download the latest firmware update from Fujitsu's official support website for the specific model
  4. 4. Follow Fujitsu's standard firmware update process - this typically requires: rebooting the system, entering BIOS/UEFI setup, selecting firmware update option, and allowing the update to complete without interruption
  5. 5. After update, verify the new firmware version matches or exceeds the fixed version for your model
Caveat Firmware updates carry inherent risk - ensure power continuity during update; backup data before proceeding; some updates may reset BIOS settings to defaults

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-2023-40238 — 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-2023-40238 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