CVE-2024-11345
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 heap-based memory vulnerability has been identified in the Postscript interpreter in various Lexmark devices. The vulnerability can be leveraged by an attacker to execute arbitrary code.
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 heap-based memory corruption vulnerability exists in the Postscript interpreter of multiple Lexmark device models. By sending specially crafted Postscript input, an attacker can trigger heap corruption and potentially achieve arbitrary code execution with the privileges of the interpreter process.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 the Lexmark device modelLocate the model number on the device label or web interface (typically under 'Device Information' or 'Settings' > 'About'). Confirm it is a Lexmark device known to have a Postscript interpreter.Affected if The device is a Lexmark model that includes Postscript interpreter functionality.
-
Check the installed firmware versionAccess the device web interface and navigate to 'Settings' > 'Firmware' or use the embedded web server status page to retrieve the current firmware version string.Affected if The installed firmware version falls within the affected version range published by Lexmark for this CVE (check Lexmark security advisory for specific version numbers).
-
Verify Postscript interpreter is enabledAccess the printer settings via the web interface or control panel. Navigate to 'Print Settings' > 'Printer Setup' or similar menu where Postscript/PCL options are configured. Confirm whether the Postscript interpreter is enabled.Affected if Postscript interpreter is enabled and accessible on the device.
-
Assess network accessibility of the Postscript serviceDetermine if the device is reachable over the network on ports used for print services (typically RAW port 9100, LPD port 515, or IPP port 631). Check firewall rules and network segmentation status.Affected if The device with Postscript interpreter enabled is directly accessible from network segments where attackers could send malicious Postscript input.
Your environment is affected if you operate a Lexmark device with a vulnerable firmware version AND the Postscript interpreter is enabled and reachable over the network.
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 the vendor-supplied firmware patch when available. If no patch exists, consider network segmentation to isolate affected devices and disable Postscript interpreter features if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11345 — 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-11345 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