CVE-2024-34397MediumMicrosoft CVSS 5.2CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Microsoft security update for CVE-2024-34397

Published
March 27, 2025
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-34397. This page also shows what EchelonGraph holds for CVE-2024-34397, 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 products6

  • azl3 glib 2.78.1-5 on Azure Linux 3.0
  • azl3 glib 2.78.6-1 on Azure Linux 3.0
  • cbl2 glib 2.71.0-5 on CBL Mariner 2.0
  • cbl2 glib 2.71.0-6 on CBL Mariner 2.0
  • cbl2 glib 2.71.0-7 on CBL Mariner 2.0
  • cbl2 glib 2.71.0-7 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 2 updates

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

KB articleUpdateFixed build
—Security Update2.78.6-1
—Security Update2.71.0-7

🧭 EchelonGraph on CVE-2024-34397

EchelonGraph score
5.2 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

An issue was discovered in GNOME GLib before 2.78.5, and 2.79.x and 2.80.x before 2.80.1. When a GDBus-based client subscribes to signals from a trusted system service such as NetworkManager on a shared computer, other users of the same computer can send spoofed D-Bus signals that the GDBus-based client will wrongly interpret as having been sent by the trusted system service. This could lead to the GDBus-based client behaving incorrectly, with an application-dependent impact.

Published by MITRE Corporation, the CVE Numbering Authority that assigned CVE-2024-34397, 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)