CVE-2024-4782
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 disrupt the printer's functionality until a manual system reboot occurs.
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 confidenceThis is a denial-of-service vulnerability in certain Lenovo printers where an unauthenticated attacker on the same network can send specially crafted requests to disrupt printer functionality. The printer becomes non-functional and requires a manual system reboot to recover, causing business disruption.
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 printer model and firmware versionAccess the printer's web console, print a configuration page, or check the device label to determine the exact model number and installed firmware version.Affected if The model and firmware version match any affected Lenovo printer models listed in Lenovo's security advisory for CVE-2024-4782.
-
Verify network accessibility of the printerCheck the printer's IP address and determine which network segment it resides on. Use network scanning tools or review VLAN configuration to identify if the printer is accessible from network segments with untrusted or unmanaged devices.Affected if The printer is reachable from network segments that contain untrusted or unmanaged devices, such as guest networks or poorly segmented office networks.
-
Confirm printer is currently operationalAttempt to access the printer's web interface, send a test print job, or ping the printer to verify it is currently responding to network requests.Affected if The printer is unresponsive or exhibits unusual behavior such as failing to process print jobs, slow response times, or intermittent connectivity issues.
-
Review recent printer access logsCheck the printer's event logs or syslog if available, for signs of unusual request patterns, failed connections, or service disruptions that may indicate exploitation attempts.Affected if Logs show multiple failed requests, unexpected source IPs, or recent service interruptions without an identified cause.
User is affected if they operate an affected Lenovo printer model with a vulnerable firmware version that is accessible from network segments with untrusted devices.
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 printers via VLAN segmentation or firewall rules, and apply any available firmware updates from Lenovo for affected printer models.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4782 — 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-4782 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