CVE-2023-47480

HIGHNVD 8.48.4
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2024-09-20. NVD baseline CVSS 8.4; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue in Pure Data 0.54-0 and fixed in 0.54-1 allows a local attacker to escalate privileges via the set*id () function.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
54(Track*)
EG Risk 54/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
Severity84% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 20, 2024

Last Modified

April 15, 2026

Advisory Details (4)

Auto-updated Sep 5, 2026
Patch available. Sources: github_commit.
generic Patch Available

[SECURITY] [DLA 3895-1] puredata security update

https://lists.debian.org/debian-lts-announce/2024/09/msg00038.html
generic

Pure Data — Pd Community Site

https://puredata.info/
generic

`set*id()` syscalls' return values not checked · Issue #2063 · pure-data/pure-data · GitHub

https://github.com/pure-data/pure-data/issues/2063
github_commit

commit 0b5e467b8728 (pure-data/pure-data)

Fix landed in pure-data/pure-data commit 0b5e467b8728 — awaiting tagged release

https://github.com/pure-data/pure-data/commit/0b5e467b8728b3ed56e1a8ee5b367ce78e7e6e5d

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
puredata0.51.4-10.51.4-1+deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
puredata0.53.1+ds-20.53.1+ds-2+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
puredata0.54.1+ds-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
puredata0.54.1+ds-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 32× 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 186 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-47480?
CVE-2023-47480 is a high vulnerability published on September 20, 2024. An issue in Pure Data 0.54-0 and fixed in 0.54-1 allows a local attacker to escalate privileges via the set*id () function.
When was CVE-2023-47480 disclosed?
CVE-2023-47480 was first published in the National Vulnerability Database on September 20, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-47480 actively exploited?
CVE-2023-47480 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.5% of all scored CVEs.
What is the CVSS score of CVE-2023-47480?
CVE-2023-47480 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2023-47480?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-47480, 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-2023-47480

Explore →

Is Your Infrastructure Affected by CVE-2023-47480?

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