CyberSecBulletin
CVE-2024-2961NVD status: Undergoing Analysis

glibc: Out-of-bounds Write

CVE-2024-2961 is a high-severity out-of-bounds write vulnerability in glibc from The GNU C Library, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 2.40 as the first without the flaw, so updating glibc to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 88.3% chance of exploitation within 30 days, which is in the top 0.23% of all scored CVEs.

Patch now

Exploitation in the next 30 days is more likely than not, according to EPSS.

What to do

  1. Update glibc to 2.40 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
The GNU C Libraryglibc2.1.93 up to, but not including, 2.402.40
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFPV3.1.5 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFPV3.1.5 and laterNot stated
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFPV3.1.5 and laterNot stated
NetAppActive Iq Unified ManagerNot specified in the recordNot stated
DebianDebian Linux10.0Not stated
NetAppHci H300s FirmwareNot specified in the recordNot stated
NetAppHci H500s FirmwareNot specified in the recordNot stated
NetAppHci H700s FirmwareNot specified in the recordNot stated
NetAppHci H410s FirmwareNot specified in the recordNot stated
NetAppHci H410c FirmwareNot specified in the recordNot stated
NetAppHci H610c FirmwareNot specified in the recordNot stated
NetAppHci H610s FirmwareNot specified in the recordNot stated
NetAppHci H615c FirmwareNot specified in the recordNot stated
NetAppHci Compute NodeNot specified in the recordNot stated
NetAppOntap Select Deploy Administration UtilityNot specified in the recordNot stated

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
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
LowSome restricted data can be read.
Integrity
LowLimited modification of data is possible.
Availability
HighThe component can be taken down completely.

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

Official description

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring 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: poc, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in glibc

All glibc vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.