CVE-2019-6489
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 Lexmark CX, MX, X, XC, XM, XS, and 6500e devices before 2019-02-11 allow remote attackers to erase stored shortcuts.
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 confidenceThis vulnerability in Lexmark multifunction printers allows remote attackers to erase stored shortcuts. The issue affects CX, MX, X, XC, XM, XS, and 6500e device models before a February 2019 firmware update. The specific attack vector and whether authentication is required are not detailed in the available description.
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<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216<= lw71.tu.p216CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 the printer modelAccess the printer's embedded web server (EWS) by entering the printer's IP address in a web browser, or print a configuration/status page from the printer's control panel. Locate the model name (such as Xm5163, Xm5170, Xm7155, Xm7163, Xm7170, Xm7155x, Xm7163x, or Xm7170x).Affected if The model is NOT one of these eight models: Xm5163, Xm5170, Xm7155, Xm7163, Xm7170, Xm7155x, Xm7163x, or Xm7170x.
-
Locate the firmware versionIn the printer's embedded web server, navigate to the Home or Status section to view the firmware version. Alternatively, on a printed configuration page, find the firmware or code level field.Affected if Unable to locate or read the firmware version from the web interface or printed page.
-
Compare firmware version against affected releaseCompare your installed firmware version to lw71.tu.p216. Note that version lw71.tu.p216 and any version with a lower numeric or alphabetic suffix are within the affected range.Affected if The firmware version is greater than lw71.tu.p216 (for example, lw71.tu.p217 or later).
-
Confirm the fix date if availableIf your firmware version appears to be after lw71.tu.p216, check the firmware release date or version notes if accessible through Lexmark support pages or the EWS. The fixed firmware was released on or after February 11, 2019.Affected if The firmware is dated after February 11, 2019 and is later than lw71.tu.p216.
A user is affected if the printer model is one of Xm5163, Xm5170, Xm7155, Xm7163, Xm7170, Xm7155x, Xm7163x, or Xm7170x AND the installed firmware version is lw71.tu.p216 or earlier.
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.
From vendor dataUpdate Lexmark device firmware to a version released on or after February 11, 2019. Review access controls and network exposure for affected devices.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6489 — 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-2019-6489 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