JetdirectHardware / appliance · Hp

CVE-2002-1048

HIGH · 7.5 CVSS v2.0 Published 2002-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
HP JetDirect printers allow remote attackers to obtain the administrative password for the (1) web and (2) telnet services via an SNMP request to the variable (.iso.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.1.0.

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 confidence

HP JetDirect printers expose administrative passwords for web and telnet services via an SNMP OID (.iso.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.1.0). Remote attackers can use SNMP read requests with default community strings to retrieve plaintext credentials and gain administrative access.

MitigationDisable SNMP or restrict SNMP access to authorized management stations, change default community strings from standard values (public/private), and update printer firmware if patches are available. Consider network isolating printers or implementing SNMPv3 with authentication.

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
JetdirectHardware / appliance
Affected:= j3111a_rev._a.08.06= j3111a_rev._g.05.35= j3111a_rev._g.07.02= j3111a_rev._g.07.03= j3111a_rev._g.07.17= j3111a_rev._g.08.03= x.08.00= x.08.04= x.08.05= x.08.20= x.08.32= x.20.00

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 HP JetDirect printer on network
    Use network scanning (e.g., nmap, SNMP queries) to discover devices. Query sysDescr OID (.1.3.6.1.2.1.1.1.0) via SNMP or check HTTP/Telnet banners for 'JetDirect' string.
    Affected if Device responds as HP JetDirect printer.
  2. Confirm SNMP is enabled
    Send SNMP GET request to the printer using community string 'public' (or 'private') targeting any standard OID like sysDescr (.1.3.6.1.2.1.1.1.0).
    Affected if SNMP request returns a valid response, indicating SNMP is active.
  3. Query vulnerability OID for password exposure
    Send SNMP GET request to OID .iso.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.1.0 using community string 'public' or 'private'.
    Affected if OID returns a plaintext administrative password string.
  4. Check firmware version against affected list
    Query firmware version via SNMP (sysDescr or printer-specific OID) or access web/telnet interface. Compare returned version to: j3111a_rev._a.08.06, j3111a_rev._g.05.35, j3111a_rev._g.07.02, j3111a_rev._g.07.03, j3111a_rev._g.07.17, j3111a_rev._g.08.03, x.08.00, x.08.04, x.08.05, x.08.20, x.08.32, x.20.00
    Affected if Installed firmware version matches one of the listed affected versions.
  5. Verify default community strings in use
    Attempt SNMP queries with community strings 'public' and 'private'. If either succeeds, default strings are active.
    Affected if SNMP access succeeds with 'public' or 'private' community string.

Environment is affected if HP JetDirect printer has SNMP enabled with default community strings AND query to OID .iso.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.1.0 returns a password, especially on listed firmware versions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable SNMP or restrict SNMP access to authorized management stations, change default community strings from standard values (public/private), and update printer firmware if patches are available. Consider network isolating printers or implementing SNMPv3 with authentication.

Fix this in Jetdirect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1048 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-1048 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