CVE-2005-2988
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 LaserJet 2430, and possibly other printers that use Jetdirect controls, stores information about recently printed documents without proper protection, which could allow remote attackers to obtain sensitive information via SNMP.
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 LaserJet 2430 and other HP printers with Jetdirect network cards store recently printed document information (likely job metadata) without proper access controls, allowing remote attackers to retrieve this sensitive data via SNMP queries.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 the printer modelAccess the printer's web interface (Jetdirect page) or check the device physically for the model number. Look for 'HP LaserJet 2430' or other HP printers with Jetdirect network cards.Affected if The device is an HP LaserJet 2430 (any firmware version) or another HP printer with Jetdirect that stores print job metadata.
-
Verify SNMP is enabledCheck the printer's Jetdirect configuration page or use an SNMP tool to query the device (e.g., snmpwalk -c public <printer_ip>). If SNMP responds, it is enabled.Affected if SNMP is enabled and responding to queries.
-
Check SNMP community string configurationAttempt SNMP queries using default community strings 'public' and 'private', or log into the Jetdirect web interface to view/configure SNMP community settings.Affected if Default SNMP community strings (public/private) are in use or SNMP has no access restrictions.
-
Test for accessible print job metadataQuery the printer via SNMP OIDs related to job history (such as .1.3.6.1.4.1.11.2.3.9.1 or vendor-specific job tracking MIBs) to see if recent print job information is returned.Affected if SNMP queries return print job metadata, document names, user names, or other job-related information to unauthenticated or unauthorized requesters.
-
Verify SNMP access restrictionsCheck the Jetdirect SNMP configuration for access control lists (ACLs) or IP-based restrictions that limit which management stations can query the device.Affected if No IP-based access restrictions are configured for SNMP, or SNMP is open to any network host.
If the device is an HP LaserJet 2430 (or HP printer with Jetdirect), SNMP is enabled with default or no access restrictions, and SNMP queries return print job metadata, the environment is affected by CVE-2005-2988.
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 dataDisable SNMP or restrict SNMP access to authorized management stations; if SNMP is required, configure SNMPv3 with authentication and encrypt traffic; apply vendor firmware updates if available.
- 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-2005-2988 — 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-2005-2988 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