CyberSecBulletin
CVE-2022-24031NVD status: Modified

RUGGEDCOM APE1808 - BIOS: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-24031 is a high-severity out-of-bounds write vulnerability in RUGGEDCOM APE1808 - BIOS from Siemens, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. The record lists version V1.0.202N as the first without the flaw, so updating RUGGEDCOM APE1808 - BIOS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.28% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update RUGGEDCOM APE1808 - BIOS to V1.0.202N or a later version.
  2. Update SIMATIC Field PG M5 to V22.01.10 or a later version.
  3. Update SIMATIC Field PG M6 to V26.01.13 or a later version.
  4. Read the advisory on insyde.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensRUGGEDCOM APE1808 - BIOSbefore V1.0.202NV1.0.202N
SiemensSIMATIC Field PG M5before V22.01.10V22.01.10
SiemensSIMATIC Field PG M6before V26.01.13V26.01.13
SiemensSIMATIC IPC127Ebefore V27.01.09V27.01.09
SiemensSIMATIC IPC227Gbefore V28.01.04V28.01.04
SiemensSIMATIC IPC277Gbefore V28.01.04V28.01.04
SiemensSIMATIC IPC277G PRObefore V28.01.04V28.01.04
SiemensSIMATIC IPC327Gbefore V28.01.04V28.01.04
SiemensSIMATIC IPC377Gbefore V28.01.04V28.01.04
SiemensSIMATIC IPC427Ebefore V21.01.17V21.01.17
SiemensSIMATIC IPC477Ebefore V21.01.17V21.01.17
SiemensSIMATIC IPC477E PRObefore V21.01.17V21.01.17
SiemensSIMATIC IPC627Ebefore V25.02.12V25.02.12
SiemensSIMATIC IPC647Ebefore V25.02.12V25.02.12
SiemensSIMATIC IPC677Ebefore V25.02.12V25.02.12
SiemensSIMATIC IPC847Ebefore V25.02.12V25.02.12
SiemensSIMATIC ITP1000before V23.01.10V23.01.10
SiemensSIPLUS IPC427Ebefore V21.01.17V21.01.17
InsydeInsydeh2o5.1 up to, but not including, 5.16.42; 5.2 up to, but not including, 5.26.42; 5.3 up to, but not including, 5.35.42; 5.4 up to, but not including, 5.43.42; 5.5 up to, but not including, 5.51.425.16.42, 5.26.42, 5.35.42, 5.43.42, 5.51.42

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.2HighNVD
CVSS 2.07.2HighNVD

Official description

An issue was discovered in NvmExpressDxe in Insyde InsydeH2O with kernel 5.1 through 5.5. An SMM memory corruption vulnerability allows an attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in RUGGEDCOM APE1808 - BIOS

All RUGGEDCOM APE1808 - BIOS vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.