CyberSecBulletin
CVE-2024-52880NVD status: Analyzed

An issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3…

Published Updated By the CyberSecBulletin desk

CVE-2024-52880 is a high-severity improper input validation vulnerability in Kernel from Insyde, with a CVSS 3.1 base score of 7.9 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 versions 5.29.50, 5.38.50, 5.46.50 as the first without the flaw, so updating Kernel to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% 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 Kernel to 5.29.50 or 5.38.50 or 5.46.50 or 5.54.50, whichever matches your release line, or a later version.
  2. Read the advisory on insyde.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
InsydeKernel5.2 up to, but not including, 5.29.50; 5.3 up to, but not including, 5.38.50; 5.4 up to, but not including, 5.46.50; 5.5 up to, but not including, 5.54.50; 5.6 up to, but not including, 5.61.50; 5.7 up to, but not including, 5.70.505.29.50, 5.38.50, 5.46.50, 5.54.50, 5.61.50, 5.70.50

Version data comes from NVD's product matching. 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
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N. Scored by CISA (ADP).

Official description

An issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3 before version 05.38.50, kernel 5.4 before version 05.46.50, kernel 5.5 before version 05.54.50, kernel 5.6 before version 05.61.50, and kernel 5.7 before version 05.70.50. In VariableRuntimeDxe driver, SecureBootHandler uses DataSize and VariableNameSize when determining if the data or name are in the buffer, but these are supplied by the caller and therefore cannot be trusted.

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

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Kernel

All Kernel vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.