Certain HP OfficeJet Pro printers are potentially vulnerable to a Denial of Service when using an improper eSCL URL GET request.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
- 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.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
- Published
- Mar 22, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 46th percentile
- CWE
- CWE-400
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hp | 1kr42a firmware | cpe:2.3:o:hp:1kr42a_firmware |
| hp | 1kr42a | cpe:2.3:h:hp:1kr42a |
| hp | 1kr45a firmware | cpe:2.3:o:hp:1kr45a_firmware |
| hp | 1kr45a | cpe:2.3:h:hp:1kr45a |
| hp | 1kr46a firmware | cpe:2.3:o:hp:1kr46a_firmware |
| hp | 1kr46a | cpe:2.3:h:hp:1kr46a |
| hp | 1kr48a firmware | cpe:2.3:o:hp:1kr48a_firmware |
| hp | 1kr48a | cpe:2.3:h:hp:1kr48a |
| hp | 1kr49a firmware | cpe:2.3:o:hp:1kr49a_firmware |
| hp | 1kr49a | cpe:2.3:h:hp:1kr49a |
| hp | 1kr54a firmware | cpe:2.3:o:hp:1kr54a_firmware |
| hp | 1kr54a | cpe:2.3:h:hp:1kr54a |
and 72 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp 1kr42a firmwarebefore 002.2349a
- hp 1kr45a firmwarebefore 002.2349a
- hp 1kr46a firmwarebefore 002.2349a
- hp 1kr48a firmwarebefore 002.2349a
- hp 1kr49a firmwarebefore 002.2349a
- hp 1kr54a firmwarebefore 002.2349a
- hp 1kr55a firmwarebefore 002.2349a
- hp 1kr55b firmwarebefore 002.2349a
- hp 1kr55d firmwarebefore 002.2349a
- hp 1mr66a firmwarebefore 002.2349a
- hp 1mr67a firmwarebefore 002.2349a
- hp 1mr68a firmwarebefore 002.2349a
- hp 1mr69a firmwarebefore 002.2349a
- hp 1mr69c firmwarebefore 002.2349a
- hp 1mr70a firmwarebefore 002.2349a
- hp 1mr71a firmwarebefore 002.2349a
- hp 1mr72a firmwarebefore 002.2349a
- hp 1mr73a firmwarebefore 002.2349a
- hp 1mr73d firmwarebefore 002.2349a
- hp 1mr74a firmwarebefore 002.2349a
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 Inc. Certain HP OfficeJet Pro Printers
- See HP Security Bulletin reference for affected versions.affected
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
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change 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.