CVE-2024-21485

Home/CVE/Versions of the package dash-core-components before 2.13.0; versions of the package dash-core-components before 2.0.0; v

CVE

Versions of the package dash-core-components before 2.13.0; versions of the package dash-core-components before 2.0.0; v

Versions of the package dash-core-components before 2.13.0.

versions of the package dash-core-components before 2.0.0.

versions of the package dash before 2.15.0.

versions of the package dash-html-components before 2.0.0.

versions of the package dash-html-components before 2.0.16 are vulnerable to Cross-site Scripting (XSS) when the href of the a tag is controlled by an adversary. An authenticated attacker who stores a view that exploits this vulnerability could steal the data that's visible to another user who opens that view - not just the data already included on the page, but they could also, in theory, make additional requests and access other data accessible to this user. In some cases, they could also steal the access tokens of that user, which would allow the attacker to act as that user, including viewing other apps and resources hosted on the same server. Note: This is only exploitable in Dash apps that include some mechanism to store user input to be reloaded by a different user.

MEDIUM · CVSS 6.5 EPSS 0.01475

Schedule remediation

Public exploit or PoC is available

Sigma rules0 YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Vulners Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2024-21485, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

View attack path from CVE-2024-21485

◆

ATT&CK techniques

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

T1190 · Exploit Public-Facing Application T1482 · Domain Trust Discovery

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-209 · XSS Using MIME Type Mismatch CAPEC-CAPEC-588 · DOM-Based XSS CAPEC-CAPEC-591 · Reflected XSS CAPEC-CAPEC-592 · Stored XSS CAPEC-CAPEC-63 · Cross-Site Scripting (XSS) CAPEC-CAPEC-85 · AJAX Footprinting

⬡

Weakness Classification

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

▤

Affected Products & Versions

plotly dash< 2.13.0

plotly dash>= 2.14.0 and < 2.15.0

▤

Affected Packages

Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.

PyPI dash MODERATE fixed in 2.15.0

PyPI dash-core-components MODERATE fixed in 2.0.0

PyPI dash-html-components MODERATE fixed in 2.0.0

npm dash-core-components MODERATE fixed in 2.13.0

npm dash-html-components MODERATE fixed in 2.0.16

⚠

Public Exploits & PoCs

These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users rate each one out of 10 (does it actually work) and can flag malware.

nucleiDash Framework - Cross-site Scriptingmedium

no ratings yet