CVE-2024-56433

LOWNVD 3.63.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 3.6 from GitHub Security Advisory (severity: LOW) published 2024-12-26. NVD baseline CVSS 3.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
3.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

CVSS v3
3.6
EG Score
3.6LOWmedium confidence
EG Risk
16
EG Risk 16/100

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 (value × EchelonGraph’s weight)
Severity36% × 45%
The EG Score, 3.6 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 26, 2024

Last Modified

April 15, 2026

Patch Availability(11)

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 rangeFix by version rangeDependents
shadow1:4.11.1+dfsg1-0exp1 ... 1:4.8.1-2 (55 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
shadow1:4.13+dfsg1-1 ... 1:4.19.3-2 (47 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
shadow1:4.17.4-2 ... 1:4.19.3-2 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
shadow1:4.17.4-2 ... 1:4.19.3-2 (10 versions)
  • every version on: no fix on record
—

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 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 186 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-56433?
CVE-2024-56433 is a low-severity vulnerability; its CVE record was published on December 26, 2024. shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by…
When was the CVE record for CVE-2024-56433 published?
The CVE record for CVE-2024-56433 was published on December 26, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-56433 actively exploited?
CVE-2024-56433 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56433?
CVE-2024-56433 has a CVSS v3 base score of 3.6 (NVD).
How do I remediate CVE-2024-56433?
A fix for CVE-2024-56433 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56433 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-56433?

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