CVE-2022-24900

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 73.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 9.9Exploit: NoneExposed: 0

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

Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer. Version 1.3 and prior are vulnerable to a path traversal attack. The os.path.join call is unsafe for use with untrusted input. When the os.path.join call encounters an absolute path, it ignores all the parameters it has encountered till that point and starts working with the new absolute path. Since the "malicious" parameter represents an absolute path, the result of os.path.join ignores the static directory completely. Hence, untrusted input is passed via the os.path.join call to flask.send_file can lead to path traversal attacks. A patch with a fix is available on the master branch of the GitHub repository. This can also be fixed by preventing flow of untrusted data to the vulnerable send_file function. In case the application logic necessiates this behaviour, one can either use the flask.safe_join to join untrusted paths or replace flask.send_file calls with flask.send_from_directory calls.

CVSS v3
9.9
EG Score
9.9(medium)
EPSS
94.1%
KEV
Not listed

Published

April 29, 2022

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Jul 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, github_commit.
github Patch Available🟡 PoC Available

Absolute Path Traversal due to incorrect use of `send_file` call · Advisory · onlaj/Piano-LED-Visualizer · GitHub

https://github.com/onlaj/Piano-LED-Visualizer/security/advisories/GHSA-g78x-q3x8-r6m4
github_pr Patch Available

Fix Path Traversal Vulnerability

Patch available: onlaj/Piano-LED-Visualizer v1.4 (PR #351 merged 2022-04-29)

https://github.com/onlaj/Piano-LED-Visualizer/pull/351
generic🟡 PoC Available

Issue · GitHub

https://github.com/onlaj/Piano-LED-Visualizer/issues/350
github_commit Patch Available

commit 3f10602323cd (onlaj/Piano-LED-Visualizer)

Patch available: onlaj/Piano-LED-Visualizer v1.4 (contains commit 3f10602323cd)

https://github.com/onlaj/Piano-LED-Visualizer/commit/3f10602323cd8184e1c69a76b815655597bf0ee5
generic

Piano-LED-Visualizer/webinterface/views_api.py at 6a732caa812c83a807c711f3d091af99209cae7b · onlaj/Piano-LED-Visualizer · GitHub

https://github.com/onlaj/Piano-LED-Visualizer/blob/6a732caa812c83a807c711f3d091af99209cae7b/webinterface/views_api.py#L970

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2022/CVE-2022-24900.yaml
    First seen Jan 1, 2022

    Piano LED Visualizer 1.3 - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-24900?
CVE-2022-24900 is a critical vulnerability published on April 29, 2022. Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer. Version 1.3 and prior are vulnerable to a path traversal attack. The os.path.join call is unsafe for use with untrusted input. When the os.path.join call encounters an absolute…
When was CVE-2022-24900 disclosed?
CVE-2022-24900 was first published in the National Vulnerability Database on April 29, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24900 actively exploited?
CVE-2022-24900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-24900?
CVE-2022-24900 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2022-24900?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-24900, 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

Explore the affected products and dependency analysis for CVE-2022-24900

Explore →

Is Your Infrastructure Affected by CVE-2022-24900?

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

Start Free Scan →Browse All CVEs