HP has identified a potential security vulnerability before IG_11_00_00.10 for DesignJet T790, T795, T1300, T2300, before MRY_04_05_00.5 for
HP has identified a potential security vulnerability before IG_11_00_00.10 for DesignJet T790, T795, T1300, T2300, before MRY_04_05_00.5 for DesignJet T920, T930, T1500, T1530, T2500, T2530, before AENEAS_03_04_00.9 for DesignJet T3500, before NEXUS_01_12_00.11 for Latex 310, 330, 360, 370, before NEXUS_03_12_00.15 for Latex 315, 335, 365, 375, before STORM_00_05_01.6 for Latex 560, 570 and Latex 110 that may expose the credentials of the SMTP server configured to receive and process emails generated by the printers.
- Published
- Jan 23, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hp | t790 firmware | cpe:2.3:o:hp:t790_firmware |
| hp | t790 | cpe:2.3:h:hp:t790 |
| hp | t795 firmware | cpe:2.3:o:hp:t795_firmware |
| hp | t795 | cpe:2.3:h:hp:t795 |
| hp | t1300 firmware | cpe:2.3:o:hp:t1300_firmware |
| hp | t1300 | cpe:2.3:h:hp:t1300 |
| hp | t2300 firmware | cpe:2.3:o:hp:t2300_firmware |
| hp | t2300 | cpe:2.3:h:hp:t2300 |
| hp | t920 firmware | cpe:2.3:o:hp:t920_firmware |
| hp | t920 | cpe:2.3:h:hp:t920 |
| hp | t930 firmware | cpe:2.3:o:hp:t930_firmware |
| hp | t930 | cpe:2.3:h:hp:t930 |
and 32 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp 110 firmwareup to nexus_00_04_53.8 inclusive
- hp 310 firmwareup to nexus_01_12_00.10 inclusive
- hp 315 firmwareup to nexus_03_12_00.14 inclusive
- hp 330 firmwareup to nexus_01_12_00.10 inclusive
- hp 335 firmwareup to nexus_03_12_00.14 inclusive
- hp 360 firmwareup to nexus_01_12_00.10 inclusive
- hp 365 firmwareup to nexus_03_12_00.14 inclusive
- hp 370 firmwareup to nexus_01_12_00.10 inclusive
- hp 375 firmwareup to nexus_03_12_00.14 inclusive
- hp 560 firmwareup to storm_00_05_01.5 inclusive
- hp 570 firmwareup to storm_00_05_01.5 inclusive
- hp t1300 firmwareup to ig_11_00_00.09 inclusive
- hp t1500 firmwareup to mry_04_05_00.4 inclusive
- hp t1530 firmwareup to mry_04_05_00.4 inclusive
- hp t2300 firmwareup to ig_11_00_00.09 inclusive
- hp t2500 firmwareup to mry_04_05_00.4 inclusive
- hp t2530 firmwareup to mry_04_05_00.4 inclusive
- hp t3500 firmwareup to aeneas_03_04_00.8 inclusive
- hp t790 firmwareup to ig_11_00_00.09 inclusive
- hp t795 firmwareup to ig_11_00_00.09 inclusive
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. HP Designjet printers; HP Latex printers
- fixed in IG_11_00_00.10, MRY_04_05_00.5, and AENEAS_03_04_00.9, NEXUS_01_12_00.11, NEXUS_03_12_00.15, and STORM_00_05_01.6affected
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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.