CVE-2020-11158
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 · uneditedu'Null pointer dereference in HP OfficeJet Pro 8210 jbig2 filter due to lack of check of PDF font array leads to denial of service' in IPS PDF releases prior to IPS System 2020.2
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 JBIG2 filter of HP OfficeJet Pro 8210 printers. The vulnerability stems from insufficient validation of PDF font arrays within the IPS PDF software component. When processing specially crafted PDF documents, the lack of proper bounds checking on font array parameters causes the JBIG2 filter to dereference a null pointer, resulting in denial of service conditions.
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 dataall versionsCVSS 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.
-
Confirm device modelCheck the printer model by printing a configuration page or accessing the embedded web server at the printer's IP address. Look for 'OfficeJet Pro 8210' in the device information.Affected if The device is not an HP OfficeJet Pro 8210 printer (this CVE only affects that specific model).
-
Identify IPS PDF software versionAccess the printer's embedded web server or check the firmware version information in the device settings. Look for the IPS PDF component version information.Affected if All versions of Qualcomm IPS PDF software are affected (no version is explicitly stated as patched in the provided data).
-
Verify JBIG2 filter is availableCheck the printer's PDF processing or filter configuration settings through the web interface or by reviewing the supported image filters. Look for JBIG2 filter status.Affected if The JBIG2 filter is enabled or available on the device (the vulnerability triggers when this filter processes a specially crafted PDF).
-
Confirm PDF processing is enabledCheck if the printer accepts PDF documents for printing through any enabled input channel (email-to-print, web upload, network share).Affected if PDF document processing is enabled and the device accepts PDF input from users or network sources.
You are affected if the device is an HP OfficeJet Pro 8210 with any version of IPS PDF software and the JBIG2 filter is available while PDF processing is enabled.
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 the IPS PDF software to IPS System 2020.2 or later to obtain the patched JBIG2 filter with proper font array validation. If immediate patching is not feasible, restrict the processing of untrusted PDF documents through the affected device.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11158 — 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-2020-11158 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