CVE-2024-52533

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-11-12. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient for a trailing '\0' character.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
67%
KEV
Not listed

Published

November 11, 2024

Last Modified

June 17, 2025

Advisory Details (6)

Auto-updated Sep 3, 2026
Patch available.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20241206-0009/
generic Patch Available

[SECURITY] [DLA 3962-1] glib2.0 security update

https://lists.debian.org/debian-lts-announce/2024/11/msg00020.html
generic

oss-security - CVE-2024-52533: Buffer overflow in socks proxy code in glib < 2.82.1

http://www.openwall.com/lists/oss-security/2024/11/12/11
generic

Home · Wiki · Teams / Releng / Security · GitLab

https://gitlab.gnome.org/Teams/Releng/security/-/wikis/home
generic

2.82.1 · GNOME / GLib · GitLab

https://gitlab.gnome.org/GNOME/glib/-/releases/2.82.1
generic

(CVE-2024-52533) Buffer overflow in set_connect_msg() (#3461) · Issues · GNOME / GLib · GitLab

https://gitlab.gnome.org/GNOME/glib/-/issues/3461

Vendor Advisories for CVE-2024-52533(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibglib2.0-tests (2.48.2-0ubuntu4.8+esm4) @ xenial2026-05-23ubuntu
redhatglib2-0:2.56.4-162.el8_82025-09-02redhat
redhatglib2-0:2.56.4-8.el8_2.22025-09-02redhat
redhatglib2-0:2.56.4-158.el8_6.22025-09-02redhat
redhatglib2-0:2.56.4-10.el8_4.22025-09-02redhat
redhatinsights-proxy/insights-proxy-container-rhel9:1.5.5-17545043432025-08-07redhat
redhatglib2-0:2.68.4-5.el9_0.22025-07-30redhat
redhatrhosdt/jaeger-rhel8-operator:rhosdt-3.6-17532653142025-07-23redhat
redhatglib2-0:2.68.4-7.el9_2.22025-07-17redhat
redhatglib2-0:2.68.4-14.el9_4.32025-07-17redhat
redhatglib2-0:2.56.4-166.el8_102025-07-16redhat
redhatglib2-0:2.68.4-16.el9_6.22025-07-15redhat
redhatglib2-0:2.80.4-4.el10_0.62025-07-14redhat
redhatmingw-glib2-0:2.78.6-2.el92025-02-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
glib2.02.66.8-1, 2.66.8-1+deb11u1, 2.66.8-1+deb11u2, 2.66.8-1+deb11u3, 2.66.8-1+deb11u42.66.8-1+deb11u5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glib2.02.74.6-2, 2.74.6-2+deb12u1, 2.74.6-2+deb12u2, 2.74.6-2+deb12u3, 2.74.6-2+deb12u42.74.6-2+deb12u5—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glib2.0—2.82.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glib2.0—2.82.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 150 total refreshes for this CVE.

  1. 2026-09-04 13:59 UTCEPSS rescore
  2. 2026-09-04 05:05 UTCEPSS rescore
  3. 2026-09-02 14:10 UTCEPSS rescore
  4. 2026-09-01 18:33 UTCOSV refresh
  5. 2026-09-01 13:52 UTCEPSS rescore
  6. 2026-09-01 13:52 UTCEPSS rescore
  7. 2026-09-01 04:37 UTCEPSS rescore
  8. 2026-08-30 19:16 UTCEPSS rescore
  9. 2026-08-30 01:20 UTCEPSS rescore
  10. 2026-08-28 21:39 UTCEPSS rescore
  11. 2026-08-27 14:23 UTCEPSS rescore
  12. 2026-08-26 14:44 UTCEPSS rescore
  13. 2026-08-25 13:47 UTCEPSS rescore
  14. 2026-08-24 14:15 UTCEPSS rescore
  15. 2026-08-23 00:18 UTCEPSS rescore
  16. 2026-08-21 23:47 UTCEPSS rescore
  17. 2026-08-20 22:54 UTCEPSS rescore
  18. 2026-08-19 17:02 UTCEPSS rescore
  19. 2026-08-19 17:02 UTCEPSS rescore
  20. 2026-08-18 13:46 UTCEPSS rescore
  21. 2026-08-17 13:45 UTCEPSS rescore
  22. 2026-08-16 14:54 UTCEPSS rescore
  23. 2026-08-16 02:13 UTCEPSS rescore
  24. 2026-08-15 20:07 UTCOSV refresh
  25. 2026-08-15 01:29 UTCEPSS rescore
Show 75 more
  1. 2026-08-13 21:59 UTCEPSS rescore
  2. 2026-08-12 13:49 UTCEPSS rescore
  3. 2026-08-11 13:40 UTCEPSS rescore
  4. 2026-08-10 23:58 UTCEPSS rescore
  5. 2026-08-09 13:45 UTCEPSS rescore
  6. 2026-08-08 16:35 UTCEPSS rescore
  7. 2026-08-07 16:25 UTCEPSS rescore
  8. 2026-08-06 13:45 UTCEPSS rescore
  9. 2026-08-05 19:16 UTCEPSS rescore
  10. 2026-08-04 15:08 UTCEPSS rescore
  11. 2026-08-04 10:36 UTCEPSS rescore
  12. 2026-08-03 10:34 UTCEPSS rescore
  13. 2026-08-02 02:25 UTCEPSS rescore
  14. 2026-08-01 04:14 UTCEPSS rescore
  15. 2026-08-01 04:14 UTCEPSS rescore
  16. 2026-07-31 12:42 UTCOSV refresh
  17. 2026-07-30 16:26 UTCEPSS rescore
  18. 2026-07-30 01:29 UTCEPSS rescore
  19. 2026-07-28 15:35 UTCEPSS rescore
  20. 2026-07-27 14:11 UTCEPSS rescore
  21. 2026-07-26 14:53 UTCEPSS rescore
  22. 2026-07-26 14:53 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:16 UTCEPSS rescore
  25. 2026-07-24 14:16 UTCEPSS rescore
  26. 2026-07-23 14:17 UTCEPSS rescore
  27. 2026-07-23 14:17 UTCEPSS rescore
  28. 2026-07-23 02:43 UTCEG score recompute
  29. 2026-07-22 14:07 UTCEPSS rescore
  30. 2026-07-22 14:07 UTCEPSS rescore
  31. 2026-07-21 15:23 UTCEPSS rescore
  32. 2026-07-20 17:06 UTCEPSS rescore
  33. 2026-07-19 02:28 UTCEPSS rescore
  34. 2026-07-19 02:28 UTCEPSS rescore
  35. 2026-07-18 10:03 UTCEPSS rescore
  36. 2026-07-18 10:03 UTCEPSS rescore
  37. 2026-07-16 17:02 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 16:56 UTCEPSS rescore
  40. 2026-07-15 01:59 UTCEPSS rescore
  41. 2026-07-15 01:59 UTCEPSS rescore
  42. 2026-07-13 22:29 UTCEPSS rescore
  43. 2026-07-13 20:08 UTCOSV refresh
  44. 2026-07-13 06:12 UTCEPSS rescore
  45. 2026-07-12 05:45 UTCEPSS rescore
  46. 2026-07-12 05:45 UTCEPSS rescore
  47. 2026-07-11 08:26 UTCEPSS rescore
  48. 2026-07-09 19:09 UTCEPSS rescore
  49. 2026-07-09 19:09 UTCEPSS rescore
  50. 2026-07-08 15:14 UTCEPSS rescore
  51. 2026-07-07 13:45 UTCEPSS rescore
  52. 2026-07-06 16:26 UTCEPSS rescore
  53. 2026-07-06 02:22 UTCEPSS rescore
  54. 2026-07-05 02:29 UTCEPSS rescore
  55. 2026-07-04 06:30 UTCEPSS rescore
  56. 2026-07-01 15:05 UTCEPSS rescore
  57. 2026-06-30 23:21 UTCEPSS rescore
  58. 2026-06-29 14:05 UTCEPSS rescore
  59. 2026-06-28 14:07 UTCEPSS rescore
  60. 2026-06-28 04:55 UTCEPSS rescore
  61. 2026-06-28 04:55 UTCEPSS rescore
  62. 2026-06-27 03:07 UTCEPSS rescore
  63. 2026-06-27 03:07 UTCEPSS rescore
  64. 2026-06-25 17:46 UTCOSV refresh
  65. 2026-06-25 13:49 UTCEPSS rescore
  66. 2026-06-24 14:04 UTCEPSS rescore
  67. 2026-06-24 14:04 UTCEPSS rescore
  68. 2026-06-23 21:32 UTCEPSS rescore
  69. 2026-06-23 21:32 UTCEPSS rescore
  70. 2026-06-22 14:25 UTCEPSS rescore
  71. 2026-06-22 14:25 UTCEPSS rescore
  72. 2026-06-21 14:56 UTCEPSS rescore
  73. 2026-06-21 01:59 UTCEPSS rescore
  74. 2026-06-21 01:58 UTCEPSS rescore
  75. 2026-06-19 19:25 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-52533?
CVE-2024-52533 is a critical vulnerability published on November 11, 2024. gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4CONNMSG_LEN is not sufficient for a trailing '\0' character.
When was CVE-2024-52533 disclosed?
CVE-2024-52533 was first published in the National Vulnerability Database on November 11, 2024, with the most recent update on June 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-52533 actively exploited?
CVE-2024-52533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 32.5% of all scored CVEs.
What is the CVSS score of CVE-2024-52533?
CVE-2024-52533 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-52533?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-52533, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-52533

Explore →

Is Your Infrastructure Affected by CVE-2024-52533?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs