CVE-2019-6326
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 · uneditedHP Color LaserJet Pro M280-M281 Multifunction Printer series (before v. 20190419), HP LaserJet Pro MFP M28-M31 Printer series (before v. 20190426) may have embedded web server attributes which may be potentially vulnerable to Buffer Overflow.
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 Color LaserJet Pro M280-M281 Multifunction Printer series and HP LaserJet Pro MFP M28-M31 Printer series contain a buffer overflow vulnerability in their embedded web server. The vulnerability exists in web server attributes and could allow remote attackers to execute arbitrary code or cause denial of service. The affected firmware versions are before 20190419 for M280-M281 series and before 20190426 for M28-M31 series.
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< 2019-04-19< 2019-04-19< 2019-04-19< 2019-04-19< 2019-04-26< 2019-04-26< 2019-04-26< 2019-04-26CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify printer model numberLocate the model label on the printer (usually on the front or inside the top cover) or access the printer's configuration page. Common model numbers for this CVE include T6b80a, T6b81a, T6b82a, T6b83a (M280-M281 series) and W2g54a, W2g55a, Y5s53a, Y5s55a (M28-M31 series).Affected if The printer model matches one of the listed product numbers.
-
Retrieve firmware versionAccess the printer's embedded web server by entering its IP address in a browser, then navigate to the General Information or About page. Alternatively, print a configuration page from the printer's control panel to view the firmware date/version.Affected if The firmware version cannot be retrieved or shows a date code.
-
Compare firmware date to thresholdIf the printer is M280-M281 series (T6b80a, T6b81a, T6b82a, T6b83a), check if the firmware date is before 20190419. If the printer is M28-M31 series (W2g54a, W2g55a, Y5s53a, Y5s55a), check if the firmware date is before 20190426.Affected if The firmware date code is earlier than 20190419 for M280-M281 models or earlier than 20190426 for M28-M31 models.
-
Verify web server accessibilityAttempt to reach the printer's web interface by navigating to http://<printer-ip> in a browser. The vulnerability exists in the embedded web server attributes, so the service must be running for exploitation.Affected if The web interface is accessible and responds, indicating the HTTP service is enabled.
If the printer model matches one of the affected product numbers AND the firmware date predates the relevant threshold AND the embedded web server is accessible, the environment is affected by this CVE.
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 data2019-04-192019-04-26
Apply the vendor-supplied firmware update to versions released on or after April 19, 2019 (M280-M281) and April 26, 2019 (M28-M31). If patching is not immediately possible, restrict network access to the printer's web management interface and disable unused HTTP services.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6326 — 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-6326 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