CVE-2018-11230
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 · uneditedjbig2_add_page in jbig2enc.cc in libjbig2enc.a in jbig2enc 0.29 allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted file.
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 use-after-free vulnerability exists in the jbig2_add_page function in jbig2enc.cc within libjbig2enc.a in jbig2enc version 0.29. Processing a specially crafted JBIG2-encoded file can cause memory to be accessed after being freed, leading to denial of service or potentially arbitrary code execution.
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.29CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 if jbig2enc is installedRun 'which jbig2enc' or 'dpkg -l | grep jbig2enc' (Debian) or 'rpm -qa | grep jbig2enc' (RHEL) to locate the jbig2enc binary or packageAffected if jbig2enc is present on the system
-
Determine the installed jbig2enc versionRun 'jbig2enc --version' or check the package version from the package manager query performed aboveAffected if The installed version is exactly 0.29
-
Locate the jbig2enc library fileSearch for libjbig2enc.a using 'find /usr -name libjbig2enc.a 2>/dev/null' or check within the installation directory of jbig2encAffected if libjbig2enc.a exists on the system
-
Identify applications or workflows that use jbig2encReview any custom applications, scripts, or document processing pipelines that invoke jbig2enc or link against libjbig2enc.a; check logs or documentation for JBIG2 encoding usageAffected if There is an application or workflow that processes JBIG2-encoded files using jbig2enc version 0.29
A system is affected if jbig2enc version 0.29 is installed and there exists any workflow or application that uses it to process JBIG2-encoded files.
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 dataAvoid processing untrusted or unknown JBIG2 files with jbig2enc. If a patched version becomes available, upgrade promptly. Consider sandboxing or restricting file processing to trusted sources only.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11230 — 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-11230 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