CVE-2021-44737
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 · uneditedPJL directory traversal vulnerability in Lexmark devices through 2021-12-07 that can be leveraged to overwrite internal configuration files.
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 · high confidenceA Printer Job Language (PJL) directory traversal vulnerability in Lexmark devices allows attackers to navigate outside the intended directory and overwrite internal configuration files, potentially modifying device settings, credentials, or enabling further exploitation.
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< mslsg.076.294< mxlsg.076.294< mslbd.076.294< mslbd.076.294< mslbd.076.294< mslbd.076.294< mslbd.076.294< mslbd.076.294CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Lexmark device modelAccess the device web interface or check the physical label to confirm the exact model number (e.g., B2236, Mb2236, Ms431, Ms331, M1342, B3442, B3340, Xm1342)Affected if The device model is NOT one of the eight affected models listed in the CVE (B2236, Mb2236, Ms431, Ms331, M1342, B3442, B3340, Xm1342)
-
Retrieve the firmware versionLog into the Lexmark embedded web server (EWS) via HTTP/HTTPS, navigate to 'Reports' > 'Device Information' or check the 'General' settings page to view the firmware version stringAffected if The installed firmware version is equal to or higher than the threshold: mslsg.076.294 (for B2236/Mb2236) or mslbd.076.294 (for all other listed models)
-
Compare against affected version rangesMatch your device model to its corresponding version threshold and verify whether the installed version falls below: B2236/Mb2236 < mslsg.076.294; Ms431/Ms331/M1342/B3442/B3340/Xm1342 < mslbd.076.294Affected if The installed firmware version is below the specified threshold for your exact model, indicating you are running a vulnerable version
-
Verify PJL service accessibilityCheck if port 9100 (default PJL port) is open and reachable on the device by running 'nc -zv <device-ip> 9100' or scanning the device with nmapAffected if The PJL service (port 9100) is exposed to untrusted networks and the device model and firmware version match the vulnerable criteria
You are affected if your device is one of the eight listed Lexmark models running firmware below the specified thresholds AND the PJL service is network-accessible.
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.
dbcve · scopedApply available firmware updates from Lexmark and restrict network access to printer devices to trusted users only.
Firmware mslsg.076.294 or higher (B2236); mxlsg.076.294 or higher (Mb2236); mslbd.076.294 or higher (Ms431, Ms331, M1342, B3442, B3340, Xm1342)
- 1. Identify the exact Lexmark model number from the affected list (B2236, Mb2236, Ms431, Ms331, M1342, B3442, B3340, or Xm1342)
- 2. Check the current firmware version on the device through the embedded web server or device status page
- 3. Navigate to the official Lexmark support site at support.lexmark.com
- 4. Locate the firmware download section for the specific model
- 5. Download the fixed firmware version: mslsg.076.294 or higher for B2236; mxlsg.076.294 or higher for Mb2236; mslbd.076.294 or higher for Ms431, Ms331, M1342, B3442, B3340, and Xm1342
- 6. Upload and apply the firmware update through the device's firmware update utility or web interface
- 7. Verify the firmware version after update to confirm the patch was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44737 — 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-2021-44737 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