CVE-2024-1869
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 HP DesignJet print products are potentially vulnerable to information disclosure related to accessing memory out-of-bounds when using the general-purpose gateway (GGW) over port 9220.
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 DesignJet printers contain an information disclosure vulnerability where accessing the general-purpose gateway (GGW) service on port 9220 triggers an out-of-bounds memory read, potentially exposing sensitive data from device memory to remote attackers.
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< axp2cn2331ar< AXP2CN2331ARCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 DesignJet modelLocate the product label on your printer or check the device inventory - look for model numbers CQ893C or CQ891CAffected if Your model is HP CQ893C or HP CQ891C
-
Determine the installed firmware versionAccess the printer's web interface (EWS) or print a configuration/customer support page to view the current firmware version stringAffected if The firmware version is below AXP2CN2331AR (or axp2cn2331ar)
-
Check if port 9220 is accessibleUse a network scanner or telnet/nc command to test TCP connectivity to port 9220 on the printer's IP addressAffected if Port 9220 responds to external network connections
-
Verify GGW service exposureAttempt an HTTP request to http://<printer-ip>:9220/ or use a tool to probe the GGW endpoint on port 9220Affected if The GGW service accepts connections from untrusted network segments
You are affected if you have an HP CQ893C or CQ891C printer with firmware below AXP2CN2331AR and the GGW service on port 9220 is accessible from your network.
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 · scopedApply HP firmware updates when released; as an interim control, block or restrict access to port 9220 via network segmentation or firewall rules to limit exposure to trusted internal systems only.
AXP2CN2331AR (or axp2cn2331ar) firmware version
- Identify your HP DesignJet model (Cq893c or Cq891c)
- Navigate to HP support website (support.hp.com) and locate drivers/firmware for your specific model
- Download the firmware version AXP2CN2331AR or later for your device
- Follow HP's firmware update instructions, typically via the printer's embedded web server or HP Utility software
- Ensure the general-purpose gateway (GGW) on port 9220 is disabled during the update process if not needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1869 — 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-1869 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