Arbitrary command execution via unsanitized speech text
Published Apr 18, 2021 · Updated Sep 16, 2024
Command injection in picotts 0.1.1 and earlier allows remote attackers to execute arbitrary operating-system commands via crafted speech text. The say function passes attacker-controlled text to child_process.exec without sanitizing shell metacharacters. Exploitation requires an application to pass untrusted text into say, after which commands run with the privileges of the hosting Node.js process.
Summary
What happened
Command injection in picotts 0.1.1 and earlier allows remote attackers to execute arbitrary operating-system commands via crafted speech text. The say function passes attacker-controlled text to child_process.exec without sanitizing shell metacharacters. Exploitation requires an application to pass untrusted text into say, after which commands run with the privileges of the hosting Node.js process.
The record
- CVE
- CVE-2021-23378
- Published
- Apr 18, 2021
- Updated
- Sep 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, CWE-77, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Snyk picotts command-injection 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