dbcve.org
B2236 FirmwareOperating system · Lexmark

CVE-2022-29850

HIGH · 8.1 CVSS v3.1 Published 2022-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Various Lexmark products through 2022-04-27 allow an attacker who has already compromised an affected Lexmark device to maintain persistence across reboots.

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

This is a post-exploitation persistence vulnerability in various Lexmark products. An attacker who has already achieved initial compromise of an affected device can establish persistence mechanisms that survive device reboots, allowing continued unauthorized access even after the device restarts.

MitigationApply available Lexmark firmware updates to address the persistence mechanism. If device compromise is suspected, perform a full device hard reset or reimage to eliminate any established persistent threats.

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.081.014
Mb2236 FirmwareOperating system
Affected:< mxlsg.081.014
Ms331 FirmwareOperating system
Affected:< mslbd.081.014
Ms431 FirmwareOperating system
Affected:< mslbd.081.014
M1342 FirmwareOperating system
Affected:< mslbd.081.014
B3442 FirmwareOperating system
Affected:< mslbd.081.014
B3340 FirmwareOperating system
Affected:< mslbd.081.014
Xm1342 FirmwareOperating system
Affected:< mslbd.081.014

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 device model and firmware version
    Access the printer's embedded web server (EWS) by entering its IP address in a browser, then navigate to the Support or About page to view the firmware version. Alternatively, print a configuration or status page from the printer's control panel menu.
    Affected if The displayed firmware version is lower than the listed thresholds for your specific model.
  2. Match firmware version to affected product line
    Locate your exact model (B2236, Mb2236, Ms331, Ms431, M1342, B3442, B3340, or Xm1342) and note the firmware version string shown (such as mslg.xxx.xxx, mxlsg.xxx.xxx, or mslbd.xxx.xxx).
    Affected if The firmware version prefix matches your product line but the numeric portion is less than 081.014.
  3. Compare version strings against thresholds
    For B2236 and Mb2236 models: check if version is below mslg.081.014 or mxlsg.081.014 respectively. For Ms331, Ms431, M1342, B3442, B3340, and Xm1342: check if version is below mslbd.081.014.
    Affected if Your installed version falls below the 081.014 threshold for your model's firmware branch.
  4. Inspect for unauthorized configuration changes
    Review the printer's EWS for unknown user accounts, altered access controls, or unexpected scheduled tasks. Check the firmware integrity or backup settings if available.
    Affected if Unexpected configurations or accounts exist that were not intentionally set by your administrators.

Your device is affected if it runs a Lexmark firmware version below 081.014 for your specific model and you suspect or have confirmed unauthorized access to the device.

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 available Lexmark firmware updates to address the persistence mechanism. If device compromise is suspected, perform a full device hard reset or reimage to eliminate any established persistent threats.

Recommended fix High confidence

Firmware mslbd.081.014 (or mslsg.081.014 for B2236, mxlsg.081.014 for Mb2236)

  1. Identify the specific Lexmark model number (B2236, Mb2236, Ms331, Ms431, M1342, B3442, B3340, or Xm1342) from the device label or web interface
  2. Access the device web interface or console to determine the current firmware version
  3. Navigate to Lexmark's official support site (support.lexmark.com) and locate the firmware download page for the specific model
  4. Download the firmware update: mslbd.081.014 for Ms331, Ms431, M1342, B3442, B3340, Xm1342; mslsg.081.014 for B2236; mxlsg.081.014 for Mb2236
  5. Follow Lexmark's documented firmware update procedure (typically via the device's Firmware Update utility or through the web interface under Maintenance > Firmware Update)
  6. After upgrading, verify the firmware version has been successfully updated to or above the fixed version
  7. Reboot the device to confirm the update persists and the device functions normally

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-2022-29850 — 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-2022-29850 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