CVE-2023-32643
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 · uneditedA flaw was found in GLib. The GVariant deserialization code is vulnerable to a heap buffer overflow introduced by the fix for CVE-2023-32665. This bug does not affect any released version of GLib, but does affect GLib distributors who followed the guidance of GLib developers to backport the initial fix for CVE-2023-32665.
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 confidenceGLib's GVariant deserialization code contains a heap buffer overflow vulnerability. This flaw was introduced as a regression in the fix for CVE-2023-32665 and only affects GLib distributors who followed the guidance to backport that initial fix. The vulnerability does not impact any officially released versions of GLib.
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.75.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Determine installed GLib versionRun 'glib-compile-schema --version' or check /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (or equivalent path for your architecture) using 'ldd --version' or 'pkg-config --modversion glib-2.0'Affected if Version is below 2.75.1 AND was obtained by backporting the CVE-2023-32665 fix rather than through official release channels
-
Identify GLib distribution sourceCheck your system's package manager (dpkg -l libglib2.0-0, rpm -qa glib2, or apk list glib) to see if this is a distribution-provided package or a custom-built versionAffected if GLib was built from source with a backported patch rather than using an official distribution package
-
Verify GVariant deserialization is in useSearch your application code or environment for calls to g_variant_new_* or g_variant_get_* functions, which trigger the vulnerable deserialization code pathAffected if Your application or any library you depend on uses GVariant serialization/deserialization
-
Confirm backport lineageReview any internal build logs, patches applied, or consult with your system administrator to determine if CVE-2023-32665 was backported to your GLib versionAffected if The installed GLib contains a backported fix for CVE-2023-32665 rather than the corrected official release
You are affected only if you are using a GLib version below 2.75.1 that was created by backporting the CVE-2023-32665 fix - standard distribution packages are not impacted.
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.
dbcve · scoped2.75.1
Organizations should verify whether they are using a backported version of the CVE-2023-32665 fix and update to the corrected version. End-users of mainstream distributions are not affected.
2.75.1 or later
- Upgrade GLib to version 2.75.1 or later to resolve the heap buffer overflow in GVariant deserialization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32643 — 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-2023-32643 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