CVE-2019-16240
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 Buffer Overflow and Information Disclosure issue exists in HP OfficeJet Pro Printers before 001.1937C, and HP PageWide Managed Printers and HP PageWide Pro Printers before 001.1937D exists; A maliciously crafted print file might cause certain HP Inkjet printers to assert. Under certain circumstances, the printer produces a core dump to a local device.
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 buffer overflow vulnerability exists in HP OfficeJet Pro and PageWide printers that allows remote attackers to cause assertion failures via maliciously crafted print files. The overflow triggers core dump generation to local storage, exposing sensitive device information including memory contents.
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< 001.1937d< 001.1937d< 001.1937d< 001.1937d< 001.1937d< 001.1937d< 001.1937d< 001.1937dCVSS 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
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 your HP printer modelLocate the model number on the printer label or access the printer's embedded web server by entering its IP address in a browserAffected if The model number matches one of: K9z76a, K9z76b, K9z76d, D3q21a, D3q21b, D3q21c, D3q21d, or 2dr21d (PageWide Pro 577z, 577dw, or 552dw)
-
Retrieve the current firmware versionFrom the printer's embedded web server, navigate to the Support or General (or About) page to view the firmware revision, or print a configuration page from the printer control panelAffected if The firmware version is displayed as a number below 001.1937d (for example, 001.1936 or earlier)
-
Check if core dump storage is enabledAccess the printer's embedded web server and look under Settings, Security, or Advanced settings for options related to core dump, debug logs, or crash data storage; on some models this may require checking the diagnostic or maintenance menuAffected if Core dump or crash dump functionality is enabled and the printer is accessible on the network to remote attackers
You are affected if you have an HP PageWide Pro model 577z, 577dw, or 552dw with firmware version below 001.1937d, and the printer is network-accessible with core dump features 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.
dbcve · scoped001.1937d
Update printer firmware to version 001.1937C or later for OfficeJet Pro, and 001.1937D or later for PageWide Managed/Pro devices. Restrict printer network access and disable core dump functionality if updating is not immediately feasible.
Firmware version 001.1937D (or later) for HP PageWide Pro printers; Firmware version 001.1937C (or later) for HP OfficeJet Pro printers
- Identify the exact printer model number (e.g., Pagewide Pro 577z K9z76a) from the printer label or control panel
- Navigate to support.hp.com and enter the printer model in the search bar
- Select 'Software and Drivers' for the specific printer model
- Locate the firmware update in the results - look for firmware version 001.1937D or later for PageWide Pro printers
- Download the firmware update file (typically .exe for Windows or .dmg for macOS)
- Run the firmware update utility and ensure the printer is connected via USB or network
- Follow the on-screen instructions to complete the firmware upgrade
- After upgrade, verify the firmware version by printing a configuration page from the printer control panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16240 — 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-16240 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