CyberSecBulletin
CVE-2023-52356NVD status: Analyzed

Red Hat Enterprise Linux 10: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2023-52356 is a high-severity out-of-bounds write vulnerability in Red Hat Enterprise Linux 10 from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.72% chance of exploitation within 30 days, higher than 86% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update iPadOS to 16.7.9 or 17.6, whichever matches your release line, or a later version.
  2. Update Iphone OS to 16.7.9 or 17.6, whichever matches your release line, or a later version.
  3. Update macOS to 12.7.6 or 13.6.8 or 14.6, whichever matches your release line, or a later version.
  4. Read the advisory on access.redhat.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.6 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat AI Inference Server 3.2Not specified in the recordNot stated
Red HatRed Hat AI Inference Server 3.3Not specified in the recordNot stated
Red HatRed Hat Discovery 2Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 6Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
DebianDebian Linux10.0; 11.0Not stated
AppleiPadOSbefore 16.7.9; 17.0 up to, but not including, 17.616.7.9, 17.6
AppleIphone OSbefore 16.7.9; 17.0 up to, but not including, 17.616.7.9, 17.6
ApplemacOSbefore 12.7.6; 13.0 up to, but not including, 13.6.8; 14.0 up to, but not including, 14.612.7.6, 13.6.8, 14.6
AppletvOSbefore 17.617.6
AppleVisionosbefore 1.31.3
ApplewatchOSbefore 10.610.6
LibTIFFLibtiffbefore 4.6.04.6.0
Red HatAi Inference Server3.2.0 up to, but not including, 3.2.2; 3.3.03.2.2
Red HatCodeready Linux Builder8.0; 9.0; 10.0Not stated
Red HatCodeready Linux Builder EUS9.6; 10.0Not stated
Red HatDiscovery2.0Not stated
Red HatEnterprise Linux6.0; 7.0; 8.0; 9.0; 10.0Not stated
Red HatEnterprise Linux EUS9.6; 10.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
NetworkCan be exploited remotely over a network, including the internet.
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
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (redhat.com)
CVSS 3.17.5HighNVD

Official description

A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service.

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: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Other vulnerabilities in Red Hat Enterprise Linux 10

All Red Hat Enterprise Linux 10 vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.