CVE-1999-1062
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 printers with JetDirect cards, when configured with TCP/IP, allow remote attackers to bypass print filters by directly sending PostScript documents to TCP ports 9099 and 9100.
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 confidenceHP LaserJet printers with JetDirect network cards configured for TCP/IP allow direct PostScript document submission to ports 9099 and 9100, bypassing print filters and enabling remote attackers to send potentially malicious print jobs directly to the printer without sanitization.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HP LaserJet with JetDirectLocate network printer documentation, check device inventory, or scan the network for HP JetDirect devices (typically identified by SNMP sysDescr or HTTP config page showing 'Jetdirect' in the product name)Affected if The device is an HP LaserJet printer with a JetDirect network card installed
-
Verify TCP/IP protocol is enabled on JetDirectAccess JetDirect configuration page (typically http://<printer_ip>/ or via telnet to port 23) and check network protocol settings, or query via SNMP for hrDeviceDescr or jetDirectTCPEnabled OIDAffected if TCP/IP is listed as an enabled network protocol in JetDirect settings
-
Confirm ports 9099 and 9100 are openRun a port scan against the printer's IP address: nmap -p 9099,9100 <printer_ip> or use netcat: nc -zv <printer_ip> 9099 9100Affected if Either port 9099 or 9100 returns as open/accepting connections
-
Check if direct print protocol is enabledIn JetDirect web config (http://<printer_ip>/), navigate to Security or Ports settings and verify 'Direct IP Printing' or 'Raw TCP Printing' is enabled, or check if SNMP shows jetDirectPrintEnable = 1Affected if Direct printing via TCP ports 9099/9100 is permitted in JetDirect configuration
-
Test direct print submission is possibleAttempt to send a raw TCP connection to port 9100 with a simple test payload (e.g., echo -e "@PJL INFO STATUS\n" | nc <printer_ip> 9100) and verify the printer responds without authenticationAffected if Connection succeeds and printer accepts jobs without authentication or filter sanitization
Your environment is affected if you have an HP LaserJet printer with JetDirect configured for TCP/IP where ports 9099 or 9100 are open and direct print submission is allowed without authentication or filtering.
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 dataRestrict network access to printer ports 9099 and 9100 via firewall rules or network segmentation, and disable direct printing protocols if centralized print server job sanitization is preferred.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1062 — 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-1999-1062 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