CVE-2019-6327
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 an IPP Parser 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 · high confidenceA buffer overflow vulnerability exists in the IPP (Internet Printing Protocol) parser of HP Color LaserJet Pro M280-M281 Multifunction Printer series and HP LaserJet Pro MFP M28-M31 Printer series. This memory corruption issue in the print rendering subsystem could allow remote attackers to execute arbitrary code on affected devices.
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< 20190419< 20190419< 20190419< 20190419< 20190426< 20190426< 20190426< 20190426CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the exact printer model numberLocate the product label on the device or check the printer configuration page accessed via its IP address. Look for the model identifier such as T6b80a, T6b83a, T6b81a, T6b82a (M280-M281 series) or W2g54a, W2g55a, Y5s53a, Y5s55a (M28-M31 series).Affected if The model number matches one of the affected product identifiers listed in the CVE.
-
Determine the installed firmware versionAccess the printer web interface by entering its IP address in a browser. Navigate to the General or About page to view the firmware version. Alternatively, print a configuration page from the printer control panel to see the firmware build date.Affected if The firmware version is earlier than 20190419 for M280-M281 models, or earlier than 20190426 for M28-M31 models.
-
Verify if IPP (Internet Printing Protocol) is enabledLog into the printer web interface and navigate to the Networking or Protocols section. Look for IPP settings under the printing protocols configuration. Check whether IPP/IPP over HTTP is turned on.Affected if IPP is enabled and the firmware version falls within the vulnerable range.
-
Check IPP service accessibility from the networkFrom a networked computer, attempt to access the IPP service by querying the printer IP on port 631 (typical IPP port) using a tool like curl or telnet: curl -k http://printer_ip:631/ipp/print. Confirm whether the service responds.Affected if The IPP service is exposed on the network and the firmware version is vulnerable.
Your environment is affected if you have an HP LaserJet Pro M280-M281 or M28-M31 series printer with IPP enabled and firmware dated before 20190419 or 20190426 respectively.
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 · scoped2019041920190426
Update printer firmware to version 20190419 or later for M280-M281 series, and version 20190426 or later for M28-M31 series. If patching is not immediately possible, restrict network access to IPP services and disable unused printing protocols.
HP Color LaserJet Pro M280-M281 firmware version 20190419 or later; HP LaserJet Pro MFP M28-M31 firmware version 20190426 or later
- 1. Identify the exact model number (T6b80a, T6b81a, T6b82a, T6b83a for M280-M281 series or W2g54a, W2g55a, Y5s53a, Y5s55a for M28-M31 series) from the printer label
- 2. Power on the printer and ensure it is connected to the network or directly to a computer
- 3. Navigate to HP Support website (support.hp.com) and enter the printer model number
- 4. Locate the firmware download section for the specific printer model
- 5. Download the firmware update file - for M280-M281 series ensure version is 20190419 or later; for M28-M31 series ensure version is 20190426 or later
- 6. Transfer the firmware file to the printer using one of these methods: a) HP Smart Web Services if the printer is network-connected, b) USB direct connection using the HP Firmware Download utility, or c) Embedded Web Server (EWS) by logging into the printer's web interface and navigating to the Firmware Update section
- 7. Follow the on-screen prompts to complete the firmware installation
- 8. After installation, verify the firmware version by printing a configuration page from the printer's control panel or via EWS
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-2019-6327 — 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-6327 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