CVE-2022-24900 piano_led_visualizer_project · piano led visualizer

Piano LED Visualizer 1.3 - Local File Inclusion

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v3.1 severity
8.6High
EPSS · exploitation likelihood
8.41% Probability within 30 daysPercentile 95.0
EPSS trend
Unchanged Since 2026-10-19
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
LowFewer obstacles to exploitation
Privileges required
NoneNo authentication required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Exploit reference available No explicit exploit maturity assessment View exploit evidence
How to read the colors & trend
Higher exposureElevatedModerateLower exposureUnknown / unassessed

CVSS colors follow its reported severity. Attack-factor colors describe each requirement, not an overall risk rating. Gray also covers absence from KEV; absence does not establish safety.

EPSS display bands: below 1% blue, 1–10% amber, 10–50% orange, 50% and above red. These are presentation bands, not FIRST severity categories. The trend compares daily EPSS probabilities, not percentile ranks; “pp” means percentage points. The sparkline shows relative movement, with its vertical scale fitted to the observed scores.

Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

4 rules identified Verified 2026-09-06 View rules & research details →

WAF protection does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC assessment

CISA ADP · Assessed 2025-04-22 · SSVC 2.0.3

Exploitation
Proof-of-concept
Automatable
Yes
Technical Impact
Partial

Stakeholder-Specific Vulnerability Categorization records CISA’s assessment of exploitation, automation, and technical impact. “None reported” reflects the assessment date; it does not establish that no exploit exists. View SSVC source details.

On this page

CVE Details

Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v3.1 · security-advisories@github.com

  • Base score: 9.9
  • Base severity: CRITICAL
  • Exploitability subscore: 3.9
  • Impact subscore: 5.3
  • Assessment type: Secondary
  • Source identifier: security-advisories@github.com
  • Full vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Changed
    • Confidentiality impact: High
    • Integrity impact: Low
    • Availability impact: Low
  • Exploit maturity: Not scored

CVSS v3.1 · NVD

  • Base score: 8.6
  • Base severity: HIGH
  • Exploitability subscore: 3.9
  • Impact subscore: 4.0
  • Assessment type: Primary
  • Source identifier: nvd@nist.gov
  • Full vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Changed
    • Confidentiality impact: High
    • Integrity impact: None
    • Availability impact: None
  • Exploit maturity: Not scored

CVSS v2.0 · NVD

  • Base score: 5.0
  • Base severity: MEDIUM
  • Exploitability subscore: 10.0
  • Impact subscore: 2.9
  • Assessment type: Primary
  • Source identifier: nvd@nist.gov
  • Full vector: AV:N/AC:L/Au:N/C:P/I:N/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Authentication: None
    • Confidentiality impact: Partial
    • Integrity impact: None
    • Availability impact: None
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record · CVE record

CISA SSVC assessments

These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.

  • Provider: CISA ADP
  • Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • SSVC version: 2.0.3
  • Role: CISA Coordinator
  • Assessment timestamp: 2025-04-22T15:41:22.627051Z
  • Exploitation: poc
  • Automatable: yes
  • Technical Impact: partial
  • Source: CISA ADP in the CVE record

Exploit references

The CVE source data tags these references as exploits. A reference alone does not establish reliability or active exploitation.

Vulnerable CPE configurations

  • cpe:2.3:a:piano_led_visualizer_project:piano_led_visualizer:*:*:*:*:*:*:*:*
    • Version end (inclusive): 1.3
    • NVD match criteria ID: C572FFB7-1561-4251-B7B2-54A9A43DFE27

Vulnerability Description

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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340007 , 344360 , 347009 , 390709 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .