CVE-2013-6193
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 · uneditedUnspecified vulnerability on HP LaserJet M1522n and M2727; LaserJet Pro 100, 300, 400, CM1415fnw, CP1*, M121*, M1536dnf, and P1*; Color LaserJet CM* and CP*; and TopShot LaserJet Pro M275 printers allows remote attackers to cause a denial of service via unknown vectors.
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 · low confidenceA denial of service vulnerability affecting numerous HP LaserJet printer models. The vulnerability is unspecified in available documentation, meaning the exact technical weakness and exploitation method are not disclosed. Remote attackers can cause printers to become unavailable or unresponsive.
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= cc431a= cc434a= cc377a= cc378a= cb494a= ce710a= ce711a= ce712a= ce842a= cc372aCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 printer model numberCheck the product label on the printer or access the printer's embedded web server (EWS) by entering the printer's IP address in a browser. Look for the model number or product number (PN) displayed in the EWS homepage or system information page.Affected if The model number matches one of: cc431a, cc434a, cc377a, cc378a, cb494a, ce710a, ce711a, ce712a, ce842a, or cc372a
-
Confirm firmware versionAccess the printer's embedded web server and navigate to the 'General' or 'Support' tab to view the firmware version. Alternatively, print a configuration page from the printer control panel (usually via Settings > Reports > Configuration Page).Affected if The printer is one of the affected models listed in step 1, regardless of firmware version (since available documentation does not specify version ranges)
-
Verify network accessibilityCheck if the printer has an active IP address on the network. In the EWS, go to Networking or Network Settings. Run a ping test to the printer's IP address from a workstation.Affected if The printer is network-accessible (has an IP address) and is one of the affected models - this enables remote attackers to trigger the DoS condition
-
Check printer status for unresponsivenessAttempt to access the printer's EWS or send a test print job. Observe if the printer responds slowly, does not respond at all, or shows error messages indicating it is unavailable or stuck.Affected if The printer exhibits denial of service symptoms (unresponsive, unavailable, or stuck) and is an affected model
You are affected if your HP LaserJet printer model number matches one of the specific product numbers (cc431a, cc434a, cc377a, cc378a, cb494a, ce710a, ce711a, ce712a, ce842a, or cc372a) and the printer is network-connected, making it reachable for remote denial of service attacks.
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 dataIsolate affected printers on restricted network segments, limit exposure to untrusted networks, and apply firmware updates from HP when available. If no update exists, consider network access controls and monitoring for anomalous traffic to printers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-6193 — 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-2013-6193 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