dbcve.org
B2236 FirmwareOperating system · Lexmark

CVE-2021-44735

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 command injection vulnerability in Lexmark devices through 2021-12-07.

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 confidence

A command injection vulnerability exists in the embedded web server of Lexmark devices, allowing remote attackers to execute arbitrary operating system commands via specially crafted HTTP requests to the web interface.

MitigationApply the vendor-supplied firmware update from Lexmark to remediate this vulnerability; if no update is available, network isolate affected devices and restrict web management interface access to trusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lexmark device model
    Locate the model number on the device label or display it via the control panel menu under 'Device Information' or 'About'
    Affected if Model is B2236, Mb2236, Ms431, Ms331, M1342, B3442, B3340, or Xm1342
  2. Check firmware version
    Access the control panel, navigate to 'Device Information' or 'Reports' > 'Menu Settings Page', and record the firmware version string (such as mslg.xxxx or mslbd.xxxx)
    Affected if Firmware version is below mslg.076.294 for B2236/Mb2236, or below mslbd.076.294 for Ms331/Ms431/M1342/B3442/B3340/Xm1342
  3. Verify web server is enabled
    From the control panel, check Network/Ports settings > 'Embedded Web Server' or 'Web Server' setting, or attempt to access https://<device-ip> in a browser
    Affected if The embedded web server is accessible and enabled (required for exploitation)
  4. Confirm HTTP service availability
    Run 'curl -k https://<device-ip>' or use a browser to verify the Lexmark web interface responds on port 443/HTTPS
    Affected if The web management interface is reachable on the network (indicates attack surface is present)

A user is affected if they have a listed Lexmark model running firmware below the specified version AND the embedded web server is enabled and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update from Lexmark to remediate this vulnerability; if no update is available, network isolate affected devices and restrict web management interface access to trusted networks.

Recommended fix Moderate confidence

Firmware version 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 device's web interface or administration console
  3. 3. Navigate to the firmware update or maintenance section
  4. 4. Download the appropriate firmware version from Lexmark support (mslsg.076.294 for B2236, mxlsg.076.294 for Mb2236, or mslbd.076.294 for Ms431/Ms331/M1342/B3442/B3340/Xm1342)
  5. 5. Upload and apply the firmware update following Lexmark's standard firmware upgrade procedure
  6. 6. Verify the firmware version has been successfully updated
  7. 7. Confirm the vulnerability is remediated by checking the firmware version matches or exceeds the fixed release
Caveat Firmware upgrades on embedded devices may reset configuration; backup settings before upgrading

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

Fix this in B2236 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44735 — 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-44735 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