dbcve.org
Linux Imaging And PrintingApplication · Hp

CVE-2025-43023

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 3.25.2 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
A potential security vulnerability has been identified in the HP Linux Imaging and Printing Software documentation. This potential vulnerability is due to the use of a weak code signing key, Digital Signature Algorithm (DSA).

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

The HP Linux Imaging and Printing Software documentation uses a weak code signing key based on the Digital Signature Algorithm (DSA). DSA has known cryptographic weaknesses, particularly with small key sizes, making signatures potentially forgeable or verifiable with compromised keys.

MitigationReplace the weak DSA signing key with a modern algorithm (RSA-4096 or EdDSA) of appropriate key size, re-sign all affected documentation, and update public key distribution channels.

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
Linux Imaging And PrintingApplication
Affected:< 3.25.2

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Check if HP Linux Imaging and Printing is installed
    Run 'rpm -q hpijs' or 'dpkg -l | grep hplip' or check for /usr/bin/hpijs binary
    Affected if The package is not found or not installed
  2. Determine installed version
    Run 'rpm -q hplip' or 'dpkg -l hplip' and note the version number
    Affected if Version is present but lower than 3.25.2
  3. Locate documentation signing keys
    Search for DSA key files in the HPLIP configuration directory, typically found under /etc/hp/ or ~/.hp/ or /usr/share/hplip/
    Affected if DSA key files are present in the HPLIP key directories
  4. Inspect documentation signature configuration
    Examine HPLIP documentation signing configuration files for algorithm identifiers such as 'dsa', 'DSA', or key length indicators like '1024' or '2048'
    Affected if Configuration files reference DSA algorithm for signing
  5. Verify active documentation signatures
    If HPLIP documentation packages exist, check for associated .sig or .asc signature files and examine key type using 'gpg --list-packets' on the signature
    Affected if Signatures use DSA key type as shown in GPG packet analysis

Affected if HP Linux Imaging and Printing version is below 3.25.2 AND DSA-based keys are actively used for documentation signing in the installation.

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 3.25.2 or later
Fixed in 3.25.2
Interim mitigation

Replace the weak DSA signing key with a modern algorithm (RSA-4096 or EdDSA) of appropriate key size, re-sign all affected documentation, and update public key distribution channels.

Recommended fix Moderate confidence

3.25.2

  1. 1. Check the current version of HP Linux Imaging and Printing installed on the system
  2. 2. If version is below 3.25.2, download the latest version 3.25.2 from the official HP support website (support.hp.com)
  3. 3. Back up any existing HP printer configurations and print queues
  4. 4. Uninstall the current HP Linux Imaging and Printing package
  5. 5. Install version 3.25.2 using the standard package installation method for your distribution
  6. 6. Verify the new version is correctly installed by checking the version number
  7. 7. Reconfigure any previously configured HP printers

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

Fix this in Linux Imaging And Printing Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43023 — 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-2025-43023 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