dbcve.org
IpsApplication · Qualcomm

CVE-2019-10627

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-21
Fix available
A fix is available. Upgrade to 001.1937c / 001.1937d or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Integer overflow to buffer overflow vulnerability in PostScript image handling code used by the PostScript- and PDF-compatible interpreters due to incorrect buffer size calculation. in PostScript and PDF printers that use IPS versions prior to 2019.2 in PostScript and PDF printers that use IPS versions prior to 2019.2

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 confidence

Integer overflow in PostScript image handling code causes incorrect buffer size calculation, leading to buffer overflow. The vulnerability exists in IPS (PostScript/PDF interpreter) versions prior to 2019.2 used in PostScript and PDF-compatible printers.

MitigationUpdate IPS (PostScript/PDF interpreter) to version 2019.2 or later to patch the integer overflow and prevent buffer overflow exploitation.

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
IpsApplication
Affected:< 2019.2
D9l63a FirmwareOperating system
Affected:< 001.1937c
D9l64a FirmwareOperating system
Affected:< 001.1937c
T0g70a FirmwareOperating system
Affected:< 001.1937c
J3p65a FirmwareOperating system
Affected:< 001.1937c
J3p68a FirmwareOperating system
Affected:< 001.1937c
J6u57a FirmwareOperating system
Affected:< 001.1937d
J6u57b FirmwareOperating system
Affected:< 001.1937d

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IPS interpreter version
    Access the printer's web interface or control panel and look for PostScript/PDF interpreter version information, typically found under 'About', 'Version Info', or 'Interpreter' settings
    Affected if The displayed IPS version is less than 2019.2 or cannot be determined to be 2019.2 or later
  2. Check HP firmware version for affected models
    Navigate to the printer's settings or status page to view the firmware version - common paths include Settings > General > Firmware Version or a dedicated 'About' page
    Affected if The firmware version starts with a number less than 001.1937 for models D9l63a, D9l64a, T0g70a, J3p65a, J3p68a, or is less than 001.1937d for J6u57a/J6u57b
  3. Verify PostScript printing is enabled
    Check the printer or print server configuration to confirm PostScript printing capability is active, as the vulnerability exists in the PostScript interpreter
    Affected if PostScript printing is enabled and the interpreter version cannot be confirmed as 2019.2 or later
  4. Review interpreter logs for anomalies
    If available, examine printer or interpreter diagnostic logs for signs of image processing issues or crashes related to PostScript image handling
    Affected if Logs show unexplained image processing failures or buffer-related errors alongside a vulnerable interpreter version

You are affected if your device uses an IPS (PostScript/PDF interpreter) version prior to 2019.2, or if you have one of the listed HP firmware versions below the specified thresholds and PostScript printing is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 001.1937c / 001.1937d / 2019.2 or later
Fixed in 001.1937c001.1937d2019.2
Interim mitigation

Update IPS (PostScript/PDF interpreter) to version 2019.2 or later to patch the integer overflow and prevent buffer overflow exploitation.

Recommended fix High confidence

IPS 2019.2 and corresponding firmware 001.1937c/001.1937d or later depending on device model

  1. 1. Identify the exact printer model and current IPS version or firmware version using the printer's control panel or web interface
  2. 2. For IPS (Internet Printing System) users: Navigate to the HP support website and download IPS version 2019.2 or later
  3. 3. For firmware-based devices: Download the appropriate firmware update (001.1937c or higher for D9l63a, D9l64a, T0g70a, J3p65a, J3p68a; 001.1937d or higher for J6u57a, J6u57b) from HP support
  4. 4. Apply the firmware update via the printer's firmware update utility or web interface following HP's documented procedures
  5. 5. Verify the update was successful by checking the new IPS/firmware version matches the fixed release
  6. 6. Restart the printer to ensure all components load with the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ips Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10627 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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