In HP LaserJet Enterprise, HP PageWide Enterprise, HP LaserJet Managed, and HP OfficeJet Enterprise Printers, solution application signature
In HP LaserJet Enterprise, HP PageWide Enterprise, HP LaserJet Managed, and HP OfficeJet Enterprise Printers, solution application signature checking may allow potential execution of arbitrary code.
- Published
- Mar 27, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-347
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hp | color laserjet cm4540 mfp firmware | cpe:2.3:o:hp:color_laserjet_cm4540_mfp_firmware |
| hp | color laserjet cm4540 mfp | cpe:2.3:h:hp:color_laserjet_cm4540_mfp |
| hp | color laserjet cp5525 firmware | cpe:2.3:o:hp:color_laserjet_cp5525_firmware |
| hp | color laserjet cp5525 | cpe:2.3:h:hp:color_laserjet_cp5525 |
| hp | color laserjet enterprise flow mfp m681f firmware | cpe:2.3:o:hp:color_laserjet_enterprise_flow_mfp_m681f_firmware |
| hp | color laserjet enterprise flow mfp m681f | cpe:2.3:h:hp:color_laserjet_enterprise_flow_mfp_m681f |
| hp | color laserjet enterprise flow mfp m681z firmware | cpe:2.3:o:hp:color_laserjet_enterprise_flow_mfp_m681z_firmware |
| hp | color laserjet enterprise flow mfp m681z | cpe:2.3:h:hp:color_laserjet_enterprise_flow_mfp_m681z |
| hp | color laserjet enterprise flow mfp m682z firmware | cpe:2.3:o:hp:color_laserjet_enterprise_flow_mfp_m682z_firmware |
| hp | color laserjet enterprise flow mfp m682z | cpe:2.3:h:hp:color_laserjet_enterprise_flow_mfp_m682z |
| hp | color laserjet enterprise m552 firmware | cpe:2.3:o:hp:color_laserjet_enterprise_m552_firmware |
| hp | color laserjet enterprise m552 | cpe:2.3:h:hp:color_laserjet_enterprise_m552 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp color laserjet cm4540 mfp firmwarebefore 2308974_579754
- hp color laserjet cp5525 firmwarebefore 2308974_579753
- hp color laserjet enterprise flow mfp m681f firmwarebefore 2406087_000017
- hp color laserjet enterprise flow mfp m681z firmwarebefore 2406087_000017
- hp color laserjet enterprise flow mfp m682z firmwarebefore 2406087_000017
- hp color laserjet enterprise m552 firmwarebefore 2308974_579763
- hp color laserjet enterprise m553 firmwarebefore 2308974_579763
- hp color laserjet enterprise m651 firmwarebefore 2308974_579770
- hp color laserjet enterprise m651 firmwarebefore 2406048_029632
- hp color laserjet enterprise m652dn firmwarebefore 2406087_000016
- hp color laserjet enterprise m652n firmwarebefore 2406087_000016
- hp color laserjet enterprise m653dh firmwarebefore 2406087_000016
- hp color laserjet enterprise m653dn firmwarebefore 2406087_000016
- hp color laserjet enterprise m653x firmwarebefore 2406087_000016
- hp color laserjet enterprise m750 firmwarebefore 2308974_579776
- hp color laserjet enterprise mfp m577 firmwarebefore 2308974_579760
- hp color laserjet enterprise mfp m577 firmwarebefore 2406048_029627
- hp color laserjet enterprise mfp m681dh firmwarebefore 2406087_000017
- hp color laserjet enterprise mfp m681f firmwarebefore 2406087_000017
- hp color laserjet enterprise mfp m682dh firmwarebefore 2406087_000017
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hp). Independent of NVD's CPE analysis and usually ahead of it.
HP HP LaserJet Enterprise, HP PageWide Enterprise, HP LaserJet Managed, and HP OfficeJet Enterprise Printers
- Various, see Security Bulletinaffected
Same product
hp: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-6318HP LaserJet Enterprise printers, HP PageWide Enterprise printers, HP LaserJet Managed printers, HP Officejet Enterprise printers have an ins40Plan
- CVE-2020-28419During installation with certain driver software or application packages an arbitrary code execution could occur.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, { algorithms: ["RS256"], issuer: "https://id.example.com", audience: "portal",});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.