Heimdall Security Logo

CVE-2023-52881

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.6%
Linux•Linux•Versions : <7ffff0cc929fdfc62a74b384c4903d6496c910f0, <=6.1.*, <3d501dd326fb1c73f1b8206d4c6e1d7b15c07e27, <2087d53a66e97a5eb5d1bf558d5bef9e5f891757, 0, <0d4e0afdd6658cd21dd5be61880411a2553fd1fc, <b17a886ed29f3b70b78ccf632dad03e0c69e3c1a, 6.6.7, <3.3, 4.14.333, <=5.10.*, <=4.14.*, <3.1, 3.8, <=6.6.*, 8d15569e14cfcf9151e9e3b4c0cb98369943a2bb, <69eae75ca5255e876628ac5cee9eaab31f644b57, <458f07ffeccd17f99942311e09ef574ddf4a414a, <=5.4.*, 3.2.37, <3.5, 354e4aa391ed50a4d827ff6fc11e0667d0859b25, <=4.19.*, e252bbd8c87b95e9cecdc01350fbb0b46a0f9bf1, <3.8, 4.19.302, 5.15.143, 6.1.68, <=*, 3.4.25, 5.4.264, <=5.15.*, 6.7, <008b807fe487e0b15a3a6c39add4eb477f73e440, 2ee4432e82437a7c051c254b065fbf5d4581e1a3, 5.10.204, 3.0.58

Description

In the Linux kernel, the following vulnerability has been resolved: tcp: do not accept ACK of bytes we never sent This patch is based on a detailed report and ideas from Yepeng Pan and Christian Rossow. ACK seq validation is currently following RFC 5961 5.2 guidelines: The ACK value is considered acceptable only if it is in the range of ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT). All incoming segments whose ACK value doesn't satisfy the above condition MUST be discarded and an ACK sent back. It needs to be noted that RFC 793 on page 72 (fifth check) says: "If the ACK is a duplicate (SEG.ACK < SND.UNA), it can be ignored. If the ACK acknowledges something not yet sent (SEG.ACK > SND.NXT) then send an ACK, drop the segment, and return". The "ignored" above implies that the processing of the incoming data segment continues, which means the ACK value is treated as acceptable. This mitigation makes the ACK check more stringent since any ACK < SND.UNA wouldn't be accepted, instead only ACKs that are in the range ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT) get through. This can be refined for new (and possibly spoofed) flows, by not accepting ACK for bytes that were never sent. This greatly improves TCP security at a little cost. I added a Fixes: tag to make sure this patch will reach stable trees, even if the 'blamed' patch was adhering to the RFC. tp->bytes_acked was added in linux-4.2 Following packetdrill test (courtesy of Yepeng Pan) shows the issue at hand: 0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 +0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 +0 bind(3, ..., ...) = 0 +0 listen(3, 1024) = 0 // ---------------- Handshake ------------------- // // when window scale is set to 14 the window size can be extended to // 65535 * (2^14) = 1073725440. Linux would accept an ACK packet // with ack number in (Server_ISN+1-1073725440. Server_ISN+1) // ,though this ack number acknowledges some data never // sent by the server. +0 < S 0:0(0) win 65535 <mss 1400,nop,wscale 14> +0 > S. 0:0(0) ack 1 <...> +0 < . 1:1(0) ack 1 win 65535 +0 accept(3, ..., ...) = 4 // For the established connection, we send an ACK packet, // the ack packet uses ack number 1 - 1073725300 + 2^32, // where 2^32 is used to wrap around. // Note: we used 1073725300 instead of 1073725440 to avoid possible // edge cases. // 1 - 1073725300 + 2^32 = 3221241997 // Oops, old kernels happily accept this packet. +0 < . 1:1001(1000) ack 3221241997 win 65535 // After the kernel fix the following will be replaced by a challenge ACK, // and prior malicious frame would be dropped. +0 > . 1:1(0) ack 1001

Gravité et risque d'exploitation

CVE-2023-52881 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.61 %, ce qui la place devant 48.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <7ffff0cc929fdfc62a74b384c4903d6496c910f0, <=6.1.*, <3d501dd326fb1c73f1b8206d4c6e1d7b15c07e27, <2087d53a66e97a5eb5d1bf558d5bef9e5f891757, 0, <0d4e0afdd6658cd21dd5be61880411a2553fd1fc, <b17a886ed29f3b70b78ccf632dad03e0c69e3c1a, 6.6.7, <3.3, 4.14.333, <=5.10.*, <=4.14.*, <3.1, 3.8, <=6.6.*, 8d15569e14cfcf9151e9e3b4c0cb98369943a2bb, <69eae75ca5255e876628ac5cee9eaab31f644b57, <458f07ffeccd17f99942311e09ef574ddf4a414a, <=5.4.*, 3.2.37, <3.5, 354e4aa391ed50a4d827ff6fc11e0667d0859b25, <=4.19.*, e252bbd8c87b95e9cecdc01350fbb0b46a0f9bf1, <3.8, 4.19.302, 5.15.143, 6.1.68, <=*, 3.4.25, 5.4.264, <=5.15.*, 6.7, <008b807fe487e0b15a3a6c39add4eb477f73e440, 2ee4432e82437a7c051c254b065fbf5d4581e1a3, 5.10.204, 3.0.58) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE