CVE-2024-27912
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 · uneditedA denial of service vulnerability was reported in some Lenovo Printers that could allow an attacker to cause the device to crash by sending crafted LPD packets.
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 confidenceA denial of service vulnerability exists in Lenovo Printers where the Line Printer Daemon (LPD) service fails to properly handle crafted packets, causing the device to crash. The attack is network-based and requires no authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Verify LPD service status on the printerAccess the printer's web administration interface or control panel and navigate to Network Services or LPD settings to confirm whether the Line Printer Daemon service is enabled.Affected if LPD service is currently enabled on the printer
-
Confirm LPD port accessibilityUse a network scanner or telnet/nmap to check if port 515/TCP (LPD) is open and reachable on the printer's IP address from your local network segment.Affected if Port 515/TCP is open and accessible from network segments that contain untrusted devices
-
Identify printer model and firmware versionLocate the model number and firmware version through the printer's web interface (usually under Status or Settings), the control panel's system information menu, or the physical label on the device.Affected if The printer model and firmware version fall within the affected product ranges stated in Lenovo's security advisory for CVE-2024-27912
-
Assess network exposureReview firewall rules and network segmentation to determine whether the printer's LPD service is reachable from outside the trusted internal network or from guest/untrusted VLANs.Affected if The printer with LPD enabled is accessible from untrusted network segments or the internet
If the LPD service is enabled, accessible from untrusted networks, and the printer model/firmware version matches Lenovo's affected product list, the environment is vulnerable to CVE-2024-27912.
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 dataApply Lenovo firmware updates when available; if no update exists, disable the LPD service on affected printers or isolate them behind a firewall to limit exposure to untrusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27912 — 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-2024-27912 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