CVE-2024-34397: An issue was discovered in GNOME GLib before 2.78.5, and 2.79.x and 2.80.x before 2.80.1.
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-34397 is a GNOME GLib GDBus signal-spoofing flaw on shared computers. Another user of the same machine could make a client application believe a trusted system service sent a D-Bus signal. Business impact depends on what the affected client does with that signal.
Executive priority
Treat this as a moderate-priority platform library update, highest for shared workstations, lab systems, kiosks, and managed Linux desktops. It is not cited as actively exploited, but incorrect trust in system-service signals can create integrity-impacting application behavior.
Technical view
GNOME GLib before 2.78.5, and 2.79.x/2.80.x before 2.80.1, could misattribute spoofed D-Bus signals to trusted system services such as NetworkManager. The issue maps to CWE-290. The CVSS 3.1 score is 5.2, with high integrity impact and low availability impact reported.
Likely exposure
Exposure is most relevant on shared Linux or GNOME-derived systems where GDBus-based clients subscribe to trusted system-service signals. The bundle does not identify specific vulnerable applications beyond GLib/GDBus behavior, so application-level exposure must be confirmed locally.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The scenario requires another user on the same shared computer to send spoofed D-Bus signals that a GDBus client wrongly trusts. Impact is application-dependent, not uniformly remote or system-wide.
Researcher notes
Evidence supports a spoofed D-Bus signal authentication weakness in GLib/GDBus, with application-dependent outcomes. Avoid assuming privilege escalation or remote exploitation from the provided bundle. Research should focus on client behaviors that make security decisions from trusted service signals.
Mitigation direction
Update GNOME GLib to 2.78.5, 2.80.1, or later supported vendor builds.
Apply Debian, Fedora, and other vendor security updates for glib2.0 or glib2 packages.
Check NetApp and Siemens advisories if those vendor products are in scope.
Prioritize shared multi-user workstations and systems running GDBus-dependent desktop or system clients.
Where updates are unavailable, monitor vendor guidance and reduce untrusted shared-user access.
Validation and detection
Inventory installed GLib package versions across Linux and appliance environments.
Confirm affected branches are not below 2.78.5 or 2.80.1.
Verify distribution security advisories are applied through package metadata or asset records.
Identify GDBus-based clients that consume trusted system-service signals on shared systems.
Document vendor-specific exposure for NetApp or Siemens products before assigning remediation ownership.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-290 · source CWE mapping
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.