Command execution via disguised workflow templates
Published Jul 17, 2024 · Updated Aug 13, 2024
OS command injection in ProjectDiscovery Nuclei 3.0.0 through 3.2.9 allows local users to execute commands through a crafted workflow file. The workflow loader accepts YAML combining a workflows field with code and HTTP blocks, causing the code block to run without -code or a signature. Execution requires a user or integrating application to run the attacker-controlled file with -w; the demonstrated payload invokes sh or bash and exposes command output.
Summary
What happened
OS command injection in ProjectDiscovery Nuclei 3.0.0 through 3.2.9 allows local users to execute commands through a crafted workflow file. The workflow loader accepts YAML combining a workflows field with code and HTTP blocks, causing the code block to run without -code or a signature. Execution requires a user or integrating application to run the attacker-controlled file with -w; the demonstrated payload invokes sh or bash and exposes command output.
The record
- CVE
- CVE-2024-40641
- Published
- Jul 17, 2024
- Updated
- Aug 13, 2024
- Vendor
- ProjectDiscovery
- Product
- Nuclei
- Classifications
- CWE-78, T1059.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 3.3.0
- Affected versionversion=3.0.0 <3.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory workflow-template proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo