CVE-2024-5749
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 · uneditedCertain HP DesignJet products may be vulnerable to credential reflection which allow viewing SMTP server credentials.
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 · moderate confidenceHP DesignJet products contain a credential reflection vulnerability that allows authenticated users or attackers to view SMTP server credentials stored on the device. This credential reflection issue exposes sensitive authentication data that should not be accessible through the product's interface.
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< 001.2419b< 001.2419b< 001.2419b< 001.2419b< 001.2419b< 001.2419b< 001.2419b< 001.2419bCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine the device firmware versionAccess the HP DesignJet web interface or control panel and navigate to the About or Support section to view the installed firmware version. Compare this version against the affected range (all versions prior to 001.2419b).Affected if The installed firmware version is earlier than 001.2419b for your specific model (F9a29a, F9a29b, F9a29c, F9a29d, F9a29e, F9a29g, T5d66a, or F9a30a).
-
Verify if SMTP configuration is presentLog into the device web interface as an authenticated user and navigate to the email or SMTP settings section. Check whether an SMTP server is configured with stored credentials.Affected if SMTP server credentials are stored on the device.
-
Test for credential reflection exposureAs an authenticated user, access the SMTP configuration page or API endpoint where credentials are displayed. Observe whether the password or authentication tokens are visible in plain text or returned in the response.Affected if SMTP credentials are exposed and readable through the authenticated interface when they should be masked or hidden.
You are affected if your HP DesignJet firmware is before version 001.2419b and you have SMTP credentials configured on the device, with those credentials visible to authenticated users through the interface.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped001.2419b
Apply available HP firmware updates for affected DesignJet products. Until patches are available, restrict network access to device management interfaces and verify that default credentials have been changed.
Firmware version 001.2419b or later for affected HP DesignJet models
- Identify the specific HP DesignJet model (F9a29a, F9a29b, F9a29c, F9a29d, F9a29e, F9a29g, T5d66a, or F9a30a) from the product label or control panel
- Navigate to the HP Support website (support.hp.com) and locate the firmware download page for your specific DesignJet model
- Download the latest firmware version (001.2419b or later) from HP's official support page
- Follow HP's firmware update instructions, typically involving connecting the printer to a computer via USB or network and using the HP Firmware Download Manager utility
- After updating, verify the firmware version displays 001.2419b or higher on the printer control panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5749 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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