CVE-2019-6337
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 · uneditedFor the printers listed 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 · moderate confidenceA specially crafted print file can trigger an assertion failure in certain HP Inkjet printers, causing the device to crash. Under specific conditions, the printer will output a core dump to local storage, potentially exposing sensitive 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.1937c< 001.1937c< 001.1937c< 001.1937c< 001.1937c< 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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 printer modelPrint a configuration page or access the printer's embedded web server (EWS) via its IP address to confirm the exact model number (e.g., D9l63a, J6u57a)Affected if The model number matches any of these: D9l63a, D9l64a, T0g70a, J3p65a, J3p68a, J6u57a, J6u57b, J9v80a
-
Check firmware versionPrint a self-test or configuration page from the printer control panel, or access the EWS and navigate to the General or About page to view the firmware versionAffected if Firmware version is below 001.1937c (for D9l63a, D9l64a, T0g70a, J3p65a, J3p68a) or below 001.1937d (for J6u57a, J6u57b, J9v80a)
-
Verify core dump storage statusAccess the printer's EWS, look under Settings, Maintenance, or Advanced settings for a Core Dump, Debug Log, or Service Log storage optionAffected if Core dump or debug logging to local storage is enabled on the printer
Your environment is affected if you have one of the listed HP Inkjet printer models running firmware below the specified version thresholds, especially if core dump storage 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 data001.1937c001.1937d
Apply available firmware updates from HP for affected Inkjet printer models. If no update is available, isolate affected devices on a restricted network segment to limit exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6337 — 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-6337 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