CVE-2018-19801
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 · uneditedaubio v0.4.0 to v0.4.8 has a NULL pointer dereference in new_aubio_filterbank via invalid n_filters.
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 confidenceA NULL pointer dereference vulnerability exists in aubio library versions 0.4.0 through 0.4.8 in the new_aubio_filterbank function. When an invalid n_filters parameter is provided, the function attempts to dereference a NULL pointer, causing a crash (denial of service). This is a classic input validation failure where the function does not properly validate the n_filters parameter before use.
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.0, <= 0.4.8CVSS 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.
-
Check if aubio library is installedRun 'pkg-config --modversion aubio' or check your package manager for aubio package version. If using Python, run 'python -c "import aubio; print(aubio.version)"'Affected if aubio is installed and version cannot be determined or is within 0.4.0 to 0.4.8
-
Verify the exact aubio versionCompare your installed version against the affected range: 0.4.0 <= version <= 0.4.8. Use 'aubio -V' or check build/version.h if compiling from sourceAffected if The installed version falls within 0.4.0 through 0.4.8 inclusive
-
Identify use of new_aubio_filterbank functionSearch source code for calls to 'new_aubio_filterbank' function. Grep: 'grep -r "new_aubio_filterbank" .' in your projectAffected if Code calls new_aubio_filterbank and passes n_filters parameter from untrusted input
-
Check n_filters input validationInspect the code path where n_filters is passed to new_aubio_filterbank. Verify if validation exists ensuring n_filters is a positive integer greater than zeroAffected if n_filters parameter is passed without validation and could be zero or negative
-
Determine if application processes untrusted inputReview if user-controlled or network-sourced data flows into the n_filters parameter of new_aubio_filterbankAffected if n_filters value originates from external input (user, file, network) without bounds checking
You are affected if aubio version 0.4.0 through 0.4.8 is installed AND your code calls new_aubio_filterbank with an unvalidated n_filters parameter from external input.
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 dataUpgrade aubio to a version newer than v0.4.8 where the vulnerability has been patched, or implement input validation to ensure n_filters is within valid bounds before calling new_aubio_filterbank.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19801 — 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-2018-19801 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