CVE-2024-3566
CVE-2024-3566 — Command injection vulnerability in programing languages on Microsoft Windows operating system.
A command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function when the specific conditions are satisfied.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
7%
chance of exploitation in 30 days
CVSS base
9.8
CRITICAL
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (8)
Products (8)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | CRITICAL | — | — | cvelistV5 |
References
8 on the record
- flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/
reference
- learn.microsoft.com/en-us/archive/blogs/twistylittlepassagesallalike/everyone-quotes-command-line-arguments-the-wrong-way
reference
- kb.cert.org/vuls/id/123335
reference
- www.cve.org/CVERecord?id=CVE-2024-24576
reference
- www.cve.org/CVERecord?id=CVE-2024-1874
reference
- www.cve.org/CVERecord?id=CVE-2024-22423
reference
- www.kb.cert.org/vuls/id/123335
reference
- github.com/nu11secur1ty/Windows11Exploits/tree/main/2024/CVE-2024-3566
reference
Elsewhere on this site
- node jsevery CVE for this vendor
- go programming languageevery CVE for this vendor
- haskell programming languageevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.