CVE-2015-0928
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 · uneditedlibhtp 0.5.15 allows remote attackers to cause a denial of service (NULL pointer dereference).
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 confidencelibhtp 0.5.15 contains a NULL pointer dereference vulnerability that can be exploited remotely to cause a denial of service. The vulnerability is triggered during HTTP traffic parsing, leading to application crash when a specially crafted request is processed.
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.5.15CVSS 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.
-
Identify installed libhtp versionRun 'dpkg -l libhtp' or 'rpm -qi libhtp' or check the library file directly with 'ldconfig -p | grep libhtp' and examine the version string in the outputAffected if The version listed is 0.5.15 exactly
-
Check if libhtp is in useIdentify processes or applications that link to libhtp using 'ldd <binary>' or 'nm -D <library>' on suspected binaries, or check for libhtp loaded in memory with 'ps aux' combined with '/proc/<pid>/maps'Affected if libhtp 0.5.15 is loaded by any running process
-
Verify HTTP traffic handling is enabledCheck if the application using libhtp has HTTP parsing active - examine configuration files for HTTP inspection features, or check if the process is listening on HTTP ports (80, 443, 8080, etc.)Affected if HTTP traffic parsing is active and libhtp 0.5.15 is being used to process requests
-
Confirm Suricata or Snort usage with libhtpSince this is 'Oisf Libhtp' (Open Information Security Foundation), check if Suricata is installed via 'suricata --version' or 'dpkg -l suricata' and note the bundled libhtp version in the outputAffected if Suricata or related IDS/IPS using libhtp 0.5.15 is deployed
You are affected if libhtp version 0.5.15 is installed and actively parsing HTTP traffic, particularly in Suricata or similar network security tools.
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 dataUpdate libhtp to the latest patched version to address the NULL pointer dereference vulnerability. If no patched version is available, consider upgrading to a newer release of the library.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0928 — 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-2015-0928 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