CyberSecBulletin
CVE-2023-52612NVD status: Modified

Linux: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2023-52612 is a high-severity buffer copy without checking size of input vulnerability in Linux, 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. The record lists versions 1142d65c5b881590962ad763f94505b6dd67d2fe, e0e3f4a18784182cfe34e20c00eca11e78d53e76, 4518dc468cdd796757190515a9be7408adc8911e as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.27% 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 Linux to 1142d65c5b881590962ad763f94505b6dd67d2fe or e0e3f4a18784182cfe34e20c00eca11e78d53e76 or 4518dc468cdd796757190515a9be7408adc8911e or a5f2f91b3fd7387e5102060809316a0f8f0bc625, whichever matches your release line, or a later version.
  2. Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
  3. Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 1142d65c5b881590962ad763f94505b6dd67d2fe; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, e0e3f4a18784182cfe34e20c00eca11e78d53e76; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 4518dc468cdd796757190515a9be7408adc8911e; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, a5f2f91b3fd7387e5102060809316a0f8f0bc625; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 4df0c942d04a67df174195ad8082f6e30e7f71a5; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 7d9e5bed036a7f9e2062a137e97e3c1e77fb8759; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 71c6670f9f032ec67d8f4e3f8db4646bf5a62883; 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 up to, but not including, 744e1885922a9943458954cfea917b31064b4131; and 1 more ranges1142d65c5b881590962ad763f94505b6dd67d2fe, e0e3f4a18784182cfe34e20c00eca11e78d53e76, 4518dc468cdd796757190515a9be7408adc8911e, a5f2f91b3fd7387e5102060809316a0f8f0bc625, 4df0c942d04a67df174195ad8082f6e30e7f71a5, 7d9e5bed036a7f9e2062a137e97e3c1e77fb8759
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
LinuxLinux Kernel4.10 up to, but not including, 4.19.306; 4.20 up to, but not including, 5.4.268; 5.5 up to, but not including, 5.10.209; 5.11 up to, but not including, 5.15.148; 5.16 up to, but not including, 6.1.75; 6.2 up to, but not including, 6.6.14; 6.7 up to, but not including, 6.7.24.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14
DebianDebian Linux10.0Not 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
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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: crypto: scomp - fix req->dst buffer overflow The req->dst buffer size should be checked before copying from the scomp_scratch->dst to avoid req->dst buffer overflow problem.

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

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output 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 Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

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

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.