Header bannerHeader banner
Advisory ID:
BRLY-2022-031

[BRLY-2022-031] The stack memory leak vulnerability in DXE driver.

January 9, 2023
Severity:
Medium
CVSS Score
4.9
Public Disclosure Date:
January 9, 2022

Summary

Binarly REsearch Team has discovered a stack memory leak vulnerability that allows a potencial attacker to write stack memory to NVRAM variable.
Vendors Affected Icon

Vendors Affected

Lenovo
Qualcomm
Affected Products icon

Affected Products

ThinkPad X13s Gen 1

Potential Impact

An attacker with local privileged access can exploit this vulnerability to read the contents of the stack and use this information to exploit other vulnerabilities in DXE. A malicious code installed as a result of the vulnerability exploitation in a DXE driver could survive across an operating system (OS) boot process and runtime or modify NVRAM area on SPI flash storage (to gain persistence on target platform). Additionally, this vulnerability potentially could be used by threat actors to bypass OS security mechanisms (modify privileged memory or runtime variables), influence on the OS boot process, and in some cases would allow an attacker to hook or modify EFI Runtime services.

Summary

Binarly REsearch Team has discovered a stack memory leak vulnerability that allows a potencial attacker to write stack memory to NVRAM variable.

Vulnerability Information

  • BINARLY internal vulnerability identifier: BRLY-2022-031
  • Qualcomm PSIRT assigned CVE identifier: CVE-2022-40518
  • CVSS v3.1 Score 4.9 Medium AV:P/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Affected Lenovo firmwares with confirmed impact by Binarly REsearch Team

Fimware Module name Module SHA256 File GUID
N3HET53W/$0AN3H00.FL1 ResetRuntimeDxe 7b2cd3ade54bdb24b93a878a226c50c5cff602e166ed1f978df381e43b487e6a 3ae17db7-3cc5-4b89-9304-9549211057ef

Potential impact

An attacker with local privileged access can exploit this vulnerability to read the contents of the stack and use this information to exploit other vulnerabilities in DXE. A malicious code installed as a result of the vulnerability exploitation in a DXE driver could survive across an operating system (OS) boot process and runtime or modify NVRAM area on SPI flash storage (to gain persistence on target platform).Additionally, this vulnerability potentially could be used by threat actors to bypass OS security mechanisms (modify privileged memory or runtime variables), influence on the OS boot process, and in some cases would allow an attacker to hook or modify EFI Runtime services.

Vulnerability description

The pseudocode of the vulnerable function is shown below:

__int64 sub_32C8()
{
  int val;
  EFI_SET_VARIABLE SetVariable;
  int VariableValue;
  __int64 DataSize;

  DataSize = 4;
  if ( ExitBootServicesEventNotified() )
    return 0;

  // The following code can only be executed before ExitBootServices
  if ( (gRT->GetVariable)(L"BSPowerCycles", &gVariableGuid, 0, &DataSize, &VariableValue) )
  {
    val = 1;
    VariableValue = 0;
  }
  else
  {
    val = VariableValue + 1;
  }
  SetVariable = gRT->SetVariable;
  VariableValue = val;
  return (SetVariable)(L"BSPowerCycles", &gVariableGuid, 3, DataSize, &VariableValue);
}

As we can see from the pseudocode, the gRT->SetVariable() service is called with the DataSize value, which can be overwritten inside the gRT->GetVariable() service.

Thus, a potential attacker can write X - 4 bytes from the stack to NVRAM if writes any buffer of length X > 4 to the BSPowerCycles NVRAM variable.

In order to fix this vulnerability, the DataSize variable must be initialized before gRT->SetVariable():

  ...
  SetVariable = gRT->SetVariable;
  VariableValue = val;
  DataSize = 4;
  return (SetVariable)(L"BSPowerCycles", &gVariableGuid, 3, DataSize, &VariableValue);

Disclosure timeline

This vulnerability is subject to a 90 day disclosure deadline. After 90 days elapsed or a patch has been made broadly available (whichever is earlier), the vulnerability report will become visible to the public.

Disclosure Activity Date (YYYY-mm-dd)
Qualcomm PSIRT is notified 2022-10-21
Qualcomm PSIRT confirmed reported issue 2022-10-30
Qualcomm PSIRT assigned CVE number 2022-12-19
Qualcomm PSIRT provide patch release 2023-01-03
BINARLY public disclosure date 2023-01-09

Acknowledgements

Binarly REsearch Team

Tags
No items found.
FWHunt
See if you are impacted now with our Firmware Vulnerability Scanner