CVE-2017-11367
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 · uneditedThe shoco_decompress function in the API in shoco through 2017-07-17 allows remote attackers to cause a denial of service (buffer over-read and application crash) via malformed compressed data.
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 buffer over-read vulnerability exists in the shoco_decompress function of the shoco compression library. When processing malformed compressed data, the function reads beyond the allocated buffer boundaries, causing application crash and 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<= 2017-07-17CVSS 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.
-
Locate shoco library in the environmentSearch for libshoco.so, libshoco.a, shoco.h, or any binary that links against the shoco library using commands like 'find / -name "*shoco*"' or 'ldconfig -p | grep shoco'Affected if No shoco library is found in the system, then the CVE does not apply
-
Determine installed shoco versionCheck the version of the shoco library file or header. If using a source installation, examine the source files for version information or check the file modification date. Compare against the affected version (any release on or before 2017-07-17)Affected if The shoco version is dated 2017-07-17 or earlier, or the version string indicates a release on or before that date
-
Identify applications using shoco_decompressSearch source code for calls to shoco_decompress function, or use 'nm' or 'objdump' on binaries to see if they are linked against shoco library functionsAffected if The application calls shoco_decompress to decompress data
-
Determine if external compressed data is processedReview the application logic to verify whether it decompresses data from untrusted sources (user input, network data, file uploads)Affected if The application decompresses data from untrusted or external sources using shoco_decompress, making it vulnerable to malformed input
-
Inspect input handling before decompressionExamine the code that passes data to shoco_decompress to see if any validation or sanity checking is performed on the compressed data before it is processedAffected if No input validation exists on compressed data before calling shoco_decompress, and malformed input could be provided to the function
The environment is affected if shoco library version 2017-07-17 or earlier is present AND an application uses shoco_decompress to process compressed data from untrusted sources without input validation.
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 shoco library to a patched version if available, or implement input validation/sanitization on compressed data before decompression to reject malformed inputs.
- 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-2017-11367 — 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-2017-11367 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