CVE-2023-40238: 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.
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.9% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 7, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-312
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| insyde | insydeh2o | cpe:2.3:a:insyde:insydeh2o |
| fujitsu | lifebook e4411 | cpe:2.3:h:fujitsu:lifebook_e4411 |
| fujitsu | esprimo d556\/2 firmware | cpe:2.3:o:fujitsu:esprimo_d556\/2_firmware |
| fujitsu | esprimo d556\/2 | cpe:2.3:h:fujitsu:esprimo_d556\/2 |
| fujitsu | esprimo d6011 firmware | cpe:2.3:o:fujitsu:esprimo_d6011_firmware |
| fujitsu | esprimo d6011 | cpe:2.3:h:fujitsu:esprimo_d6011 |
| fujitsu | esprimo d6012 firmware | cpe:2.3:o:fujitsu:esprimo_d6012_firmware |
| fujitsu | esprimo d6012 | cpe:2.3:h:fujitsu:esprimo_d6012 |
| fujitsu | esprimo d7010 firmware | cpe:2.3:o:fujitsu:esprimo_d7010_firmware |
| fujitsu | esprimo d7010 | cpe:2.3:h:fujitsu:esprimo_d7010 |
| fujitsu | esprimo d7010\/8 firmware | cpe:2.3:o:fujitsu:esprimo_d7010\/8_firmware |
| fujitsu | esprimo d7010\/8 | cpe:2.3:h:fujitsu:esprimo_d7010\/8 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fujitsu celsius c780 firmwarebefore 1.28.0
- fujitsu celsius h5511 firmwarebefore 1.16
- fujitsu celsius h7510 firmwarebefore 1.17
- fujitsu celsius h7613 firmwarebefore 1.14
- fujitsu celsius h780 firmwarebefore 1.23
- fujitsu celsius h980 firmwareall versions
- fujitsu celsius j5010 firmwarebefore 1.64.0
- fujitsu celsius j550/2 firmwarebefore 1.35.0
- fujitsu celsius j580 firmwarebefore 1.38.0
- fujitsu celsius m7010 firmwarebefore 1.12.0
- fujitsu celsius m7010power firmwarebefore 1.12.0
- fujitsu celsius m7010x firmwarebefore 1.06.0
- fujitsu celsius m7010xpower firmwarebefore 1.06.0
- fujitsu celsius r970 firmwarebefore 1.14.0
- fujitsu celsius r970b firmwarebefore 1.14.0
- fujitsu celsius r970bpower firmwarebefore 1.14.0
- fujitsu celsius w5010 firmwarebefore 1.64.0
- fujitsu celsius w5010/l firmwarebefore 1.64.0
- fujitsu celsius w5011 firmwarebefore 1.31.0
- fujitsu celsius w5012 firmwarebefore 3.08.0
Same product
insyde: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-39281A stack buffer overflow vulnerability discovered in AsfSecureBootDxe in Insyde InsydeH2O with kernel 5.0 through 5.5 allows attackers to run39Monitor
- CVE-2021-41842An issue was discovered in AtaLegacySmm in the kernel 5.0 before 05.08.46, 5.1 before 05.16.46, 5.2 before 05.26.46, 5.3 before 05.35.46, 5.39Monitor
- CVE-2023-22613An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5.35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-39284Nov 2, 2023 · An issue was discovered in IhisiServicesSmm in Insyde InsydeH2O with kernel 5.0 through 5.5.22Monitor
- ← EarlierCVE-2023-39283Nov 2, 2023 · An SMM memory corruption vulnerability in the SMM driver (SMRAM write) in CsmInt10HookSmm in Insyde InsydeH2O with kernel 5.0 through 5.5 al31Monitor
- Later →CVE-2022-24351Dec 15, 2023 · TOCTOU race-condition vulnerability in Insyde InsydeH2O with Kernel 5.2 before version 05.27.29, Kernel 5.3 before version 05.36.29, Kernel 18Monitor
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.
- CVE-2023-31041115 days apartAn issue was discovered in SysPasswordDxe in Insyde InsydeH2O with kernel 5.0 through 5.5.30Monitor
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-312 · Cleartext Storage of Sensitive InformationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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)
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.