CVE-2024-11347
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 · uneditedInteger Overflow or Wraparound vulnerability in Lexmark International CX, XC, CS, et. Al. (Postscript interpreter modules) allows Forced Integer Overflow.The vulnerability can be leveraged by an attacker to execute arbitrary code as an unprivileged user.
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 confidenceInteger overflow vulnerability in Lexmark printer PostScript interpreter modules allows forced integer overflow that can be leveraged to execute arbitrary code as an unprivileged user.
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 Lexmark printers on your networkScan your network for Lexmark devices, or review your asset inventory for CX, XC, or CS series printers. Note the IP addresses and hostnames of any found devices.Affected if Any Lexmark CX, XC, or CS series printer is present on the network
-
Determine the firmware version of each deviceAccess the printer web interface or use SNMP/Lexmark diagnostic tools to retrieve the current firmware version. Compare against the version in Lexmark's security advisory for CVE-2024-11347.Affected if The installed firmware version is older than the patched version listed in Lexmark's advisory for this CVE
-
Verify if PostScript interpreter is enabledCheck the printer configuration via the web UI or printed menu page for PostScript/PS support status. This is typically found under 'Emulations' or 'Printer Languages' settings.Affected if PostScript emulation is enabled and available on the device
-
Assess network accessibility of printer servicesDetermine if the printer is accessible from network segments where unprivileged users operate. Check if raw print ports (9100) or web services are exposed beyond trusted segments.Affected if The printer and its print services are reachable from untrusted network segments
-
Confirm user access to print job submissionVerify whether standard non-privileged users have the ability to submit print jobs to the affected device, particularly jobs that could contain PostScript code.Affected if Unprivileged users can submit print jobs to the affected Lexmark device
Your environment is affected if you have Lexmark CX, XC, or CS series printers with PostScript enabled running firmware versions older than Lexmark's patched releases for CVE-2024-11347.
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 Lexmark firmware updates to affected devices (CX, XC, CS series) when released by vendor; network segmentation can limit attack surface until patching is complete.
- 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-2024-11347 — 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-11347 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