CVE-2024-4781
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 unauthenticated attacker on a shared network to crash printer communications until the system is rebooted.
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 confidenceA denial-of-service vulnerability exists in certain Lenovo printers that allows an unauthenticated attacker on a shared network segment to crash printer communications. The vulnerability can render the printer non-responsive, and recovery requires a system reboot.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify Lenovo printers on the networkScan network for devices with Lenovo vendor OUI (00-1F-3B or similar) or check DHCP lease tables for Lenovo printer hostnames. Use nmap with -sV or check SNMP sysDescr values for 'Lenovo' and 'printer'.Affected if Any Lenovo printer is found on the network without isolation from untrusted segments
-
Verify network segment exposureCheck if the printer subnet allows access from untrusted network segments. Review VLAN configuration, ACLs, and firewall rules protecting the printer subnet. Determine if the printer is on the same broadcast domain as untrusted workstations or guest networks.Affected if The printer is accessible from network segments containing untrusted or unauthenticated users
-
Confirm printer accessibility from untrusted hostsFrom a non-privileged host on an untrusted segment, attempt to reach the printer via ping, port scan (common ports: 80, 443, 9100), or curl to the web interface. This simulates the unauthenticated attacker's perspective.Affected if The printer responds to network requests from untrusted segments without authentication requirements
-
Check current printer availabilitySend ICMP echo request (ping) and attempt TCP connection to printer ports (9100 for raw print, 80/443 for web). Note any timeouts, packet loss, or incomplete responses that may indicate the printer is already non-responsive.Affected if The printer is unresponsive or shows symptoms of a denial-of-service condition
-
Document printer firmware version if accessibleIf the printer web interface or SNMP is accessible, retrieve the firmware version from system info pages. Compare against any vendor advisories or release notes for this CVE.Affected if Firmware version cannot be verified or matches known affected versions (if disclosed by vendor)
A user is affected if any Lenovo printer is present on a network segment accessible to unauthenticated attackers, as the CVE allows remote crash without authentication.
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 a restricted network segment to limit exposure to unauthenticated attackers, and apply vendor-supplied firmware updates when available. Consider implementing network access controls or firewall rules to limit traffic to trusted sources.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4781 — 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-4781 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