CyberSecBulletin
CVE-2023-34853NVD status: Modified

x12dpg-qr: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2023-34853 is a high-severity out-of-bounds write vulnerability in x12dpg-qr from Supermicro, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected x12dpg-qr versions: 1.4b. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.39% 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. Check which version of x12dpg-qr you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on supermicro.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Supermicrox12dpg-qr1.4bNot stated
SupermicroX12dai-n6 FirmwareNot specified in the recordNot stated
SupermicroX12ddw-a6 FirmwareNot specified in the recordNot stated
SupermicroX12dgo-6 FirmwareNot specified in the recordNot stated
SupermicroX12dgq-r FirmwareNot specified in the recordNot stated
SupermicroX12dgu FirmwareNot specified in the recordNot stated
SupermicroX12dhm-6 FirmwareNot specified in the recordNot stated
SupermicroX12dpd-a6m25 FirmwareNot specified in the recordNot stated
SupermicroX12dpfr-an6 FirmwareNot specified in the recordNot stated
SupermicroX12dpg-ar FirmwareNot specified in the recordNot stated
SupermicroX12dpg-oa6 FirmwareNot specified in the recordNot stated
SupermicroX12dpg-oa6-gd2 FirmwareNot specified in the recordNot stated
SupermicroX12dpg-qbt6 FirmwareNot specified in the recordNot stated
SupermicroX12dpg-qr FirmwareNot specified in the recordNot stated
SupermicroX12dpg-qt6 FirmwareNot specified in the recordNot stated
SupermicroX12dpg-u6 FirmwareNot specified in the recordNot stated
SupermicroX12dpi-n6 FirmwareNot specified in the recordNot stated
SupermicroX12dpi-nt6 FirmwareNot specified in the recordNot stated
SupermicroX12dpl-i6 FirmwareNot specified in the recordNot stated
SupermicroX12dpl-nt6 FirmwareNot specified in the recordNot stated
SupermicroX12dpt-b6 FirmwareNot specified in the recordNot stated
SupermicroX12dpt-pt46 FirmwareNot specified in the recordNot stated
SupermicroX12dpt-pt6 FirmwareNot specified in the recordNot stated
SupermicroX12dpu-6 FirmwareNot specified in the recordNot stated
SupermicroX12dsc-6 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. 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
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
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:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Official description

Buffer Overflow vulnerability in Supermicro motherboard X12DPG-QR 1.4b allows local attackers to hijack control flow via manipulation of SmcSecurityEraseSetupVar variable.

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.