CVE-2000-0013
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 · uneditedIRIX soundplayer program allows local users to gain privileges by including shell metacharacters in a .wav file, which is executed via the midikeys program.
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 · moderate confidenceThe IRIX soundplayer program's midikeys component fails to properly sanitize shell metacharacters in .wav filenames, allowing local users to inject and execute arbitrary commands with elevated privileges by including special characters like semicolons or pipes in a crafted .wav filename.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.2CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Identify the operating systemRun 'uname -s' or check /etc/issue to confirm the system is SGI IRIXAffected if The OS is not SGI IRIX (this CVE only affects IRIX)
-
Determine the IRIX versionRun 'uname -r' or check /etc/version to obtain the exact release versionAffected if The version is 6.2 (the only affected version per the CVE)
-
Locate the midikeys binarySearch for the midikeys program using 'find / -name midikeys -type f 2>/dev/null' or check typical SGI sound program directories like /usr/bin/ or /usr/local/bin/Affected if The midikeys executable is found on the system
-
Check if midikeys is executableRun 'ls -la <path_to_midikeys>' and verify execute permissions are set for any user (owner, group, or others)Affected if Execute permission bits are set for any user class (indicating the program can be run)
-
Verify soundplayer package installationCheck if the soundplayer package is installed via 'versions' or 'inst' commands common to IRIX, or look for other soundplayer components in /var/options/ or /usr/lib/Affected if The soundplayer package containing midikeys is installed
You are affected only if you are running SGI IRIX version 6.2 and have the midikeys component of the soundplayer program installed with execute permissions enabled.
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.
From vendor dataSince IRIX is end-of-life and no patches are available, the recommended remediation is to remove or restrict execution permissions on the vulnerable midikeys program, or retire the system entirely if replacement is feasible.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0013 — 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-2000-0013 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