CVE-2024-28886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOS command injection vulnerability exists in UTAU versions prior to v0.4.19. If a user of the product opens a crafted UTAU project file (.ust file), an arbitrary OS command may be executed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in UTAU's project file (.ust) parser. When a user opens a crafted .ust file containing malicious payload, the application improperly handles data during parsing and allows execution of arbitrary operating system commands on the victim's machine.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm UTAU software is installedCheck for UTAU executable on the system. Common locations: C:\Program Files\UTAU (Windows) or in user's application data folders. Look for utau.exe or similar executable files.Affected if UTAU is found installed on the system
-
Identify installed UTAU versionRight-click the UTAU executable, select Properties, then view the Details tab for the File Version. Alternatively, launch UTAU and check the version displayed in the application title bar or about dialog.Affected if The version shown is earlier than v0.4.19 (for example, v0.4.18, v0.4.17, etc.)
-
Verify .ust file association and usageCheck if .ust files are associated with UTAU by looking at file associations in the system. Inspect the Windows Registry under HKCR\.ust or check file type associations.Affected if UTAU is installed and .ust files are configured to open with UTAU (default behavior)
-
Review recent .ust file accessCheck recently opened .ust files in the system. On Windows, examine recent documents or the application's file history if available. Look for any .ust files from untrusted or unknown sources.Affected if The user has opened .ust files, particularly from untrusted sources, with a vulnerable UTAU version installed
The environment is affected if UTAU version 0.4.18 or earlier is installed and the application is used to open .ust project files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to UTAU v0.4.19 or later to obtain the patched version. Until then, avoid opening .ust files from untrusted or unknown sources.
UTAU v0.4.19
- 1. Download UTAU version 0.4.19 from the official UTAU distribution site (utau2008.xrea.jp)
- 2. Back up any existing UTAU projects (.ust files) if desired
- 3. Install or replace the existing UTAU installation with version 0.4.19
- 4. Verify the version by checking UTAU's about or version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data