CVE-2019-9633
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 · uneditedgio/gsocketclient.c in GNOME GLib 2.59.2 does not ensure that a parent GTask remains alive during the execution of a connection-attempting enumeration, which allows remote attackers to cause a denial of service (g_socket_client_connected_callback mishandling and application crash) via a crafted web site, as demonstrated by GNOME Web (aka Epiphany).
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 · high confidenceA race condition in gio/gsocketclient.c within GNOME GLib 2.59.2 fails to maintain a reference to the parent GTask object during socket connection enumeration. When the connection-attempt callback executes, it references a freed GTask object, causing a use-after-free that crashes the application. This can be triggered remotely via a malicious website in browsers like Epiphany that use this GLib component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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= 2.59.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed GLib versionRun `pkg-config --modversion glib-2.0` or check your package manager (dpkg -l | grep libglib2.0 on Debian/Ubuntu, rpm -qa | grep glib on RHEL/CentOS)Affected if The version reported is exactly 2.59.2
-
Check for GLib library file versionInspect the shared library directly with `strings /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 | grep "^2\.59\.2$"` or similar path for your architectureAffected if The library contains version string 2.59.2
-
Identify applications using GSocketClientCheck for browsers or network applications that depend on GLib (such as Epiphany/WebKitGTK) with `ldd $(which epiphany) 2>/dev/null | grep glib`Affected if Epiphany or other GLib-based network applications are installed and used with GLib 2.59.2
-
Review application crash logsExamine dmesg, journalctl, or application-specific logs for use-after-free errors in socket connection handlingAffected if Logs show crashes in gsocketclient.c or GSocketClient callbacks with memory corruption patterns
You are affected if GNOME GLib version 2.59.2 is installed and you use applications (such as Epiphany browser) that leverage GSocketClient for network connections.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade GNOME GLib to version 2.60 or later which contains the patched GTask lifecycle management in gsocketclient.c. Until patched, restrict browser access to untrusted web content.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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