CVE-2025-60019: Glib-networking: uninitialized memory dereferences on glib-networking through glib-networking/tls/openssl/gtlsbio.c via g_tls_bio_new_from_iostream() and g_tls_bio_new_from_datagram_based()
glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60019 is a low-severity reliability issue in glib-networking's OpenSSL backend. Under out-of-memory conditions, missing allocation checks could cause an invalid memory write, with expected impact limited to reduced availability rather than data theft or privilege gain.
Executive priority
Treat as routine patch management unless local evidence shows important services depend on the affected OpenSSL backend. The documented impact is low availability degradation, not confidentiality or integrity loss.
Technical view
The issue is described as unchecked memory allocation return handling in glib-networking/tls/openssl/gtlsbio.c, affecting paths using g_tls_bio_new_from_iostream() and g_tls_bio_new_from_datagram_based(). CVSS 3.1 is 3.7 with high attack complexity and low availability impact only.
Likely exposure
Exposure appears limited to systems using glib-networking's OpenSSL backend. The bundle names glib-networking 2.60, while Red Hat Enterprise Linux 6 through 10 entries are marked default unaffected.
Exploitation context
No provided source states active exploitation, and the CVE is not listed as KEV. The described trigger depends on an out-of-memory condition, which aligns with high attack complexity and limited availability impact.
Researcher notes
Evidence supports an unchecked allocation failure leading to possible invalid memory write during TLS BIO creation. Source details do not establish a public exploit, broad product impact, or a specific fixed version.
Mitigation direction
Check GNOME and operating-system vendor guidance for fixed glib-networking packages.
Update glib-networking when a vendor-supported fix is available.
Prioritize internet-facing services that depend on glib-networking TLS functionality.
Track Red Hat status separately because listed RHEL releases are marked default unaffected.
Validation and detection
Inventory installed glib-networking versions across Linux assets.
Identify applications using glib-networking with the OpenSSL backend.
Compare package versions against GNOME and distribution advisories.
Confirm whether affected assets are exposed to untrusted network traffic.
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-476: 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-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.