dbcve.org
T790 FirmwareOperating system · Hp

CVE-2017-2747

HIGH · 7.8 CVSS v3.0 Published 2018-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
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.

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 · high confidence

HP DesignJet and Latex printer models contain a vulnerability that exposes SMTP server credentials configured for email functionality. The flaw allows unauthorized disclosure of authentication credentials stored on the printer, potentially enabling unauthorized access to the email server.

MitigationUpdate printer firmware to the patched versions (IG_11_00_00.10+, MRY_04_05_00.5+, AENEAS_03_04_00.9+, NEXUS_01_12_00.11+, NEXUS_03_12_00.15+, STORM_00_05_01.6+) and rotate exposed SMTP credentials as a precaution.

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
T790 FirmwareOperating system
Affected:<= ig_11_00_00.09
T795 FirmwareOperating system
Affected:<= ig_11_00_00.09
T1300 FirmwareOperating system
Affected:<= ig_11_00_00.09
T2300 FirmwareOperating system
Affected:<= ig_11_00_00.09
T920 FirmwareOperating system
Affected:<= mry_04_05_00.4
T930 FirmwareOperating system
Affected:<= mry_04_05_00.4
T1500 FirmwareOperating system
Affected:<= mry_04_05_00.4
T1530 FirmwareOperating system
Affected:<= mry_04_05_00.4

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify printer model and firmware version
    Access the printer's web interface (embedded web server) by entering the printer's IP address in a browser, or print a configuration/info page from the printer's front panel. Locate the model name and firmware version displayed.
    Affected if The printer model is one of: T790, T795, T1300, T2300, T920, T930, T1500, T1530, and the firmware version is at or below the affected threshold (ig_11_00_00.09 for T790/T795/T1300/T2300, or mry_04_05_00.4 for T920/T930/T1500/T1530).
  2. Check if SMTP email functionality is configured
    In the printer's web interface, navigate to the Email/SMTP or Network settings section. Look for configured email server settings, including SMTP server address, port, and any saved email accounts.
    Affected if SMTP email functionality is enabled and configured with authentication credentials on the printer.
  3. Verify credential exposure via web interface
    In the printer web interface, examine the email settings page where SMTP credentials are stored. Attempt to view or inspect the stored username and password fields for the email configuration.
    Affected if The SMTP username and password are visible in plain text or easily recoverable through the web interface without authentication beyond the printer's admin credentials.
  4. Check for unauthorized access indicators
    Review email server logs for any unauthorized access attempts from the printer's IP address or using the exposed SMTP credentials. Check if any unexpected emails were sent from the configured email account.
    Affected if Suspicious email activity is observed from the configured SMTP account, or credentials have been used from unauthorized locations.

A user is affected if they own an HP DesignJet printer from the affected model list, run firmware at or below the specified vulnerable versions, and have SMTP email functionality configured with stored credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update printer firmware to the patched versions (IG_11_00_00.10+, MRY_04_05_00.5+, AENEAS_03_04_00.9+, NEXUS_01_12_00.11+, NEXUS_03_12_00.15+, STORM_00_05_01.6+) and rotate exposed SMTP credentials as a precaution.

Fix this in T790 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2747 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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