CVE-2024-22025MediumMicrosoft CVSS 6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2024-22025

Published
June 30, 2024
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-22025. This page also shows what EchelonGraph holds for CVE-2024-22025, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • azl3 nodejs 20.10.0-2 on Azure Linux 3.0
  • azl3 nodejs 20.14.0-1 on Azure Linux 3.0
  • cbl2 nodejs 16.20.2-4 on CBL Mariner 2.0
  • cbl2 nodejs18 18.18.2-5 on CBL Mariner 2.0
  • cbl2 nodejs18 18.18.2-7 on CBL Mariner 2.0

✅ Updates Microsoft lists: 3 updates

3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update18.18.2-5
—Security Update16.20.2-4
—Security Update20.14.0-1

🧭 EchelonGraph on CVE-2024-22025

EchelonGraph score
6.5 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

A vulnerability in Node.js has been identified, allowing for a Denial of Service (DoS) attack through resource exhaustion when using the fetch() function to retrieve content from an untrusted URL. The vulnerability stems from the fact that the fetch() function in Node.js always decodes Brotli, making it possible for an attacker to cause resource exhaustion when fetching content from an untrusted URL. An attacker controlling the URL passed into fetch() can exploit this vulnerability to exhaust memory, potentially leading to process termination, depending on the system configuration.

Published by HackerOne, the CVE Numbering Authority that assigned CVE-2024-22025, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)