Arbitrary command execution via crafted project file
Published May 28, 2024 · Updated Aug 2, 2024
OS command injection in Ameya/Ayame UTAU before 0.4.19 allows context-dependent attackers to execute commands through a crafted .ust project file. Public advisories identify the crafted .ust file as the trigger but do not disclose the parser field or command-construction operation. Execution requires a user to open the malicious project, after which commands run with that user’s privileges.
Summary
What happened
OS command injection in Ameya/Ayame UTAU before 0.4.19 allows context-dependent attackers to execute commands through a crafted .ust project file. Public advisories identify the crafted .ust file as the trigger but do not disclose the parser field or command-construction operation. Execution requires a user to open the malicious project, after which commands run with that user’s privileges.
The record
- CVE
- CVE-2024-28886
- Published
- May 28, 2024
- Updated
- Aug 2, 2024
- Vendor
- Ameya/Ayame
- Product
- UTAU
- Classifications
- CWE-94, CWE-78, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <0.4.19
- Affected versionversion=prior to v0.4.19
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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