dbcve.org
B2236 FirmwareOperating system · Lexmark

CVE-2021-44734

CRITICAL · 9.8 CVSS v3.1 Developing Published 2022-01-20
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Embedded web server input sanitization vulnerability in Lexmark devices through 2021-12-07, which can which can lead to remote code execution on the device.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
B2236 FirmwareOperating system
Affected:< mslsg.076.294
Mb2236 FirmwareOperating system
Affected:< mxlsg.076.294
Ms431 FirmwareOperating system
Affected:< mslbd.076.294
Ms331 FirmwareOperating system
Affected:< mslbd.076.294
M1342 FirmwareOperating system
Affected:< mslbd.076.294
B3442 FirmwareOperating system
Affected:< mslbd.076.294
B3340 FirmwareOperating system
Affected:< mslbd.076.294
Xm1342 FirmwareOperating system
Affected:< mslbd.076.294

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Recommended fix High confidence

Upgrade to firmware mslsg.076.294 (B2236), mxlsg.076.294 (Mb2236), or mslbd.076.294 (Ms431/Ms331/M1342/B3442/B3340/Xm1342)

  1. 1. Identify the exact Lexmark device model from the affected list (B2236, Mb2236, Ms431, Ms331, M1342, B3442, B3340, or Xm1342)
  2. 2. Access the Lexmark support website at support.lexmark.com
  3. 3. Enter the device model number to locate the firmware download page
  4. 4. Download firmware version mslsg.076.294 for B2236 devices
  5. 5. Download firmware version mxlsg.076.294 for Mb2236 devices
  6. 6. Download firmware version mslbd.076.294 for Ms431, Ms331, M1342, B3442, B3340, and Xm1342 devices
  7. 7. Access the device's embedded web server (EWS) via browser using the device's IP address
  8. 8. Navigate to Settings > Firmware Update or similar firmware upgrade section
Caveat Firmware updates may briefly interrupt printing services; ensure power stability during the update process

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists B2236 Firmware has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $3,550. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-44734 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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