CVE-2019-14381
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 · uneditedlibopenmpt before 0.4.3 allows a crash due to a NULL pointer dereference when doing a portamento from an OPL instrument to an empty instrument note map slot.
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 confidencelibopenmpt before 0.4.3 contains a NULL pointer dereference vulnerability triggered when performing a portamento (smooth pitch transition) from an OPL (FM synthesis) instrument to an empty instrument note map slot. This causes a crash leading to denial of service.
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< 0.4.3CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify libopenmpt installationCheck for libopenmpt library files (.so, .dll, .dylib) or the openmpt command-line tool in your system. Look for files named libopenmpt.* or the 'openmpt123' player binary.Affected if libopenmpt is present on the system
-
Determine installed versionRun 'openmpt123 --version' or check the library version via your package manager (dpkg -l libopenmpt*, rpm -q libopenmpt, or similar). Compare the version number to 0.4.3.Affected if Version is lower than 0.4.3 (e.g., 0.4.2, 0.4.1, etc.)
-
Check for OPL instrument usageReview your music/module files being played. OPL instruments are FM synthesis instruments typically found in tracker files (MOD, S3M, XM, IT) that use OPL emulation patches.Affected if You are playing module files that contain OPL-based instruments
-
Verify portamento configurationInspect the module file for portamento effects (effect 3 or 5 in tracker formats) transitioning from an OPL instrument slot to an empty instrument slot in the note map.Affected if Portamento effects are used to transition from OPL instruments to empty instrument slots, which triggers the NULL dereference
You are affected if libopenmpt version is below 0.4.3 AND you are playing module files with OPL instruments using portamento to empty note map slots.
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 data0.4.3
Upgrade libopenmpt to version 0.4.3 or later to resolve the NULL pointer dereference issue.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14381 — 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-2019-14381 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