Libapreq2Application · Apache
CVE-2019-12412
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 · uneditedA flaw in the libapreq2 v2.07 to v2.13 multipart parser can deference a null pointer leading to a process crash. A remote attacker could send a request causing a process crash which could lead to a denial of service attack.
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 confidenceA null pointer dereference vulnerability exists in the multipart parser of libapreq2 versions 2.07 through 2.13. When processing malformed or specially crafted multipart requests, the parser can dereference a null pointer, causing the process to crash and resulting in 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
Libapreq2Application
>= 2.07, <= 2.13CVSS 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.1/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.
-
Verify if libapreq2 is installedQuery the package manager (rpm -qa | grep apreq, dpkg -l | grep apreq, or pkg-config --modversion libapreq2) or check for libapreq2.so in /usr/lib or /usr/local/libAffected if libapreq2 is present on the system
-
Determine the installed libapreq2 versionRun: pkg-config --modversion libapreq2, or check via rpm -qa | grep apreq, or examine the library file name (libapreq2.so.X.X.X) in the library directoryAffected if the version is 2.07, 2.08, 2.09, 2.10, 2.11, 2.12, or 2.13
-
Confirm multipart parsing is in useIdentify if mod_apreq (Apache module) is loaded (httpd -M 2>/dev/null | grep apreq) or if the libapreq2 library is linked into any running application (ldd <application> | grep apreq)Affected if libapreq2 is actively loaded or linked into a running service that handles HTTP multipart requests
-
Check for Apache or application handling multipart uploadsReview Apache configuration files (httpd.conf, .htaccess) for multipart handling directives or application code that processes file uploads via libapreq2Affected if the server is configured to accept multipart/form-data requests which triggers the vulnerable parser code path
The environment is affected if libapreq2 versions 2.07 through 2.13 are installed AND the library is actively handling multipart HTTP requests.
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 libapreq2 to a version beyond v2.13 (or latest stable) to patch the null pointer dereference. Implement request size limits and consider a WAF as a compensating control until the upgrade is applied.
Fix this in Libapreq2
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12412 — 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-12412 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