CVE-2024-5143
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 · uneditedA user with device administrative privileges can change existing SMTP server settings on the device, without having to re-enter SMTP server credentials. By redirecting send-to-email traffic to the new server, the original SMTP server credentials may potentially be exposed.
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 confidenceA device administrator can modify existing SMTP server settings without re-authenticating the stored SMTP credentials. This allows redirection of email traffic to an attacker-controlled server, causing the original SMTP username/password to be transmitted to the malicious server.
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< 002_2413A< 002_2413A< 002_2413A< 002_2413A< 002_2413A< 002_2413A< 002_2413A< 002_2413ACVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
-
Identify your HP printer modelCheck the product label on the device or access the printer's web interface (Embedded Web Server) to view the model number. Look for product codes W1a75a, W1a76a, W1a77a, W1a78a, W1a79a, W1a80a, W1a81a, or W1a82a.Affected if The model is one of the listed product codes and falls within the affected firmware range.
-
Check the installed firmware versionAccess the printer's Embedded Web Server, navigate to the General or Support Information page, and locate the firmware version field. Alternatively, print a configuration page from the device menu to view the firmware version.Affected if The firmware version is lower than 002_2413A (for example, 002_2401 or earlier).
-
Verify SMTP configuration statusLog into the printer's Embedded Web Server as an administrator. Navigate to the Email/SMTP or Settings > Email setup section. Check if an SMTP server is configured and enabled.Affected if SMTP is configured with stored credentials (username/password) and the firmware version is below 002_2413A.
-
Review administrator authentication behaviorIn the SMTP settings section, attempt to modify the SMTP server address or port. Observe whether the system prompts for re-authentication of the existing SMTP credentials before allowing the change.Affected if The server address can be modified without requiring re-entry or verification of the stored SMTP username and password.
Your environment is affected if you have an HP printer model W1a75a through W1a82a with firmware version below 002_2413A and SMTP is configured with stored credentials that are not re-authenticated when modifying server settings.
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 · scoped002_2413A
Require re-authentication of SMTP credentials before allowing modification of SMTP server settings, ensuring the legitimate user's identity is verified before sensitive configuration changes.
Firmware version 002_2413A or later
- Identify the specific HP printer model (W1a75a through W1a82a series) from the affected product list
- Navigate to HP support website (support.hp.com) and locate the firmware download section for your specific printer model
- Download the firmware update version 002_2413A or later
- Access the printer's Embedded Web Server (EWS) by entering the printer's IP address in a web browser
- Log in with administrator credentials
- Locate the Firmware Update section in the EWS settings
- Upload and install the downloaded firmware file
- After the update completes, verify the firmware version displays as 002_2413A or higher in the EWS or printer control panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5143 — 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-5143 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