dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-34397

MEDIUM · 5.2 CVSS v3.1 Published 2024-05-07
Fix available
A fix is available. Upgrade to 2.78.5 / 2.80.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Public exploit No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 39= 40
GlibApplication
Affected:< 2.78.5>= 2.79.0, < 2.80.1
Ontap ToolsApplication
Affected:= 10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.78.5 / 2.80.1 or later
Fixed in 2.78.52.80.1
Recommended fix High confidence

Glib 2.78.5 or Glib 2.80.1 (or later)

  1. Identify the installed glib version by running 'pkg-config --modversion glib-2.0' or 'rpm -q glib2' (RHEL/Fedora) or 'dpkg -l libglib2.0-0' (Debian)
  2. For Debian 10: Update package lists with 'apt-get update' and upgrade glib via 'apt-get upgrade libglib2.0-0' to receive the fixed package from Debian's security repositories
  3. For Fedora 39/40: Run 'dnf update glib2' to install the fixed version
  4. For systems building from source: Download glib version 2.78.5 or 2.80.1 (or later) from gnome.org or the official GNOME git repository and rebuild
  5. After upgrading glib, restart any running applications that use GDBus to ensure they load the fixed library
  6. Verify the new version is active by checking 'pkg-config --modversion glib-2.0' shows 2.78.5 or higher, or 2.80.1 or higher
Caveat Glib is a core system library; upgrading may require restarting graphical sessions or system services that depend on D-Bus functionality

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34397 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data