CVE-2012-2107
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 · uneditedInteger overflow in the main function in util/lpci_main.c in Csound before 5.17.2, when converting a file, allows user-assisted remote attackers to execute arbitrary code via a crafted file, which triggers a heap-based buffer overflow.
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 confidenceInteger overflow in the main function in util/lpci_main.c in Csound versions before 5.17.2, triggered during file conversion operations, allows attackers to cause a heap-based buffer overflow via a specially crafted input file, potentially leading to arbitrary code execution.
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<= 5.17= 5.10= 5.10.1= 5.11= 5.11.1= 5.12= 5.12.1= 5.12.3= 5.12.4= 5.13.0= 5.13.1= 5.14.0CVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Check if Csound is installedRun 'csound --version' or check for Csound binary in common locations (/usr/bin/csound, /usr/local/bin/csound)Affected if Csound is not installed or the command fails
-
Identify the installed Csound versionRun 'csound --version' and note the version number in the outputAffected if Version is 5.17 or lower, or matches any of these: 5.10, 5.10.1, 5.11, 5.11.1, 5.12, 5.12.1, 5.12.3, 5.12.4, 5.13.0, 5.13.1, 5.14.0
-
Check for the lpci utilityRun 'which lpci' or look for lpci binary in Csound installation directoriesAffected if The lpci utility exists and is accessible on the system
-
Determine if file conversion operations are performedReview any scripts or workflows that use lpci for converting .wav, .aiff, or other audio filesAffected if lpci is used to process untrusted or crafted input files
You are affected if Csound version 5.17 or lower is installed AND the lpci utility is used to process audio 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 · scopedUpgrade to Csound 5.17.2 or later. Avoid opening untrusted or crafted audio/utility files with Csound utilities until the upgrade is applied.
Csound 5.17.2 or later (preferably latest stable 5.x release)
- 1. Check the current installed version of Csound by running 'csound --version' or 'csound -V'
- 2. Download the fixed version of Csound (version 5.17.2 or later) from the official Csound repository or source archive
- 3. Uninstall the current version of Csound using the package manager (e.g., 'apt-get remove csound' on Debian/Ubuntu, 'yum remove csound' on RHEL/CentOS, or 'brew uninstall csound' on macOS)
- 4. Install the new version using the appropriate package manager or by compiling from source
- 5. Verify the installation by running 'csound --version' and confirming the version number is 5.17.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2107 — 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-2012-2107 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