CVE-2019-6334
No exploitation reported by the sources we read.
- Published2019-10-16
- Fixed in2309021_581893 · 2309021_581898 · 2309021_581886 · 2309021_581895 · 2309021_581902 · 2309021_581899
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
HP LaserJet, PageWide, OfficeJet Enterprise, and LaserJet Managed Printers have a solution to check application signature that may allow potential execution of arbitrary code.
Timeline
dates in UTC- 2019-10-1615:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-6334?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-6334?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2309021.x | < 2309021_581893 | 2309021_581893 | NVD |
| 2309021.x | < 2309021_581898 | 2309021_581898 | NVD |
| 2309021.x | < 2309021_581886 | 2309021_581886 | NVD |
| 2309021.x | < 2309021_581895 | 2309021_581895 | NVD |
| 2309021.x | < 2309021_581902 | 2309021_581902 | NVD |
| 2309021.x | < 2309021_581899 | 2309021_581899 | NVD |
| 2309021.x | < 2309021_581889 | 2309021_581889 | NVD |
| 2309021.x | < 2309021_581900 | 2309021_581900 | NVD |
| 2309021.x | < 2309021_581892 | 2309021_581892 | NVD |
| 2309021.x | < 2309021_581909 | 2309021_581909 | NVD |
| 2309021.x | < 2309021_581910 | 2309021_581910 | NVD |
| 2309021.x | < 2309021_581897 | 2309021_581897 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2408071.x | < 2408071_000209 | 2408071_000209 | NVD |
| 2408071.x | < 2408071_000205 | 2408071_000205 | NVD |
| 2408071.x | < 2408071_000142 | 2408071_000142 | NVD |
| 2408071.x | < 2408071_000121 | 2408071_000121 | NVD |
| 2408071.x | < 2408071_000187 | 2408071_000187 | NVD |
| 2408071.x | < 2408071_000203 | 2408071_000203 | NVD |
| 2408071.x | < 2408071_000190 | 2408071_000190 | NVD |
| 2408071.x | < 2408071_000197 | 2408071_000197 | NVD |
| 2408071.x | < 2408071_000181 | 2408071_000181 | NVD |
| 2408071.x | < 2408071_000120 | 2408071_000120 | NVD |
| 2408071.x | < 2408071_000103 | 2408071_000103 | NVD |
| 2408071.x | < 2408071_000196 | 2408071_000196 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Hp futuresmart 3 to 2309021_581893 · 2309021_581898 · 2309021_581886 · 2309021_581895 · 2309021_581902 · 2309021_581899 · 2309021_581889 · 2309021_581900
Advisories and patches
- support.hp.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- FIRST EPSSEPSS score3.6 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-10-16
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-6334?
Is CVE-2019-6334 actively exploited?
What is the CVSS score for CVE-2019-6334?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.