CVE-2024-11346
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 · unedited: Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in Lexmark International CX, XC, CS, et. Al. (Postscript interpreter modules) allows Resource Injection.This issue affects CX, XC, CS, et. Al.: from 001.001:0 through 081.231, from *.*.P001 through *.*.P233, from *.*.P001 through *.*.P759, from *.*.P001 through *.*.P836.
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 confidenceType confusion vulnerability in Lexmark printer PostScript interpreter allows attackers to inject malicious resources by exploiting inadequate type checking. The flaw enables an attacker to manipulate resource handling within the interpreter, potentially executing arbitrary code or causing denial of service.
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 device modelAccess the printer web interface or print a configuration page to confirm the device is a CX, XC, or CS series Lexmark printer. These are the product lines mentioned as affected.Affected if Device is a Lexmark CX, XC, or CS series printer and the firmware is older than the patched version for this CVE.
-
Check installed firmware versionLog into the printer web interface (Embedded Web Server) and navigate to 'Settings' > 'General' > 'About' to view the firmware version. Alternatively, print a menu settings page from the control panel.Affected if The installed firmware version is older than the version Lexmark released as the patch for CVE-2024-11346 (check Lexmark security advisory for the specific version number).
-
Verify PostScript interpreter is enabledAccess the printer web interface and navigate to 'Settings' > 'Print Settings' > 'PDL Settings' (Printer Description Languages) or similar menu. Check if PostScript emulation or PostScript language is enabled.Affected if PostScript emulation is enabled and the firmware version is unpatched; the vulnerability exists specifically within the PostScript interpreter module.
-
Confirm network exposureReview the printer's network configuration in the web interface under 'Network/Ports' > 'TCP/IP'. Determine if the printer is directly accessible from untrusted networks, including the internet, or if it is isolated behind a firewall/VLAN.Affected if The printer is exposed to untrusted network segments or the internet without network segmentation, increasing the likelihood of exploitation.
A user is affected if they have a Lexmark CX, XC, or CS series device with PostScript enabled and firmware version prior to the vendorpatched release for CVE-2024-11346.
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 all affected CX, XC, and CS series devices to patch the PostScript interpreter module. Prioritize devices exposed to untrusted network segments or the internet.
- 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-11346 — 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-11346 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