Skip to content
Noroxi
CVE-2021-44737· NVD / CVE Program· CNA mitre

PJL directory traversal vulnerability in Lexmark devices through 2021-12-07 that can be leveraged to overwrite internal configuration files.

HighCVSS 8.8 · v3.1—No exploit No fix recorded
Published
Jan 20, 2022
Updated
Jun 17, 2026
EPSS
1.4% · 72th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

Affected systems

VendorProduct
lexmarkb2236 firmware
lexmarkb2236
lexmarkmb2236 firmware
lexmarkmb2236
lexmarkms431 firmware
lexmarkms431
lexmarkms331 firmware
lexmarkms331
lexmarkm1342 firmware
lexmarkm1342
lexmarkb3442 firmware
lexmarkb3442

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lexmark 6500e firmwarebefore lhs60.jr.p753
  • lexmark b2236 firmwarebefore mslsg.076.294
  • lexmark b2338 firmwarebefore msngm.076.294
  • lexmark b2442 firmwarebefore msngm.076.294
  • lexmark b2546 firmwarebefore msngm.076.294
  • lexmark b2650 firmwarebefore msngm.076.294
  • lexmark b2865 firmwarebefore msngw.076.294
  • lexmark b3340 firmwarebefore mslbd.076.294
  • lexmark b3442 firmwarebefore mslbd.076.294
  • lexmark c2132 firmwarebefore lw80.vy4.p210
  • lexmark c2240 firmwarebefore cstzj.076.294
  • lexmark c2325 firmwarebefore csnzj.076.294
  • lexmark c2326 firmwarebefore cslbn.076.294
  • lexmark c2425 firmwarebefore csnzj.076.294
  • lexmark c2535 firmwarebefore csnzj.076.294
  • lexmark c3224 firmwarebefore cslbl.076.294
  • lexmark c3326 firmwarebefore cslbl.076.294
  • lexmark c3426 firmwarebefore cslbn.076.294
  • lexmark c4150 firmwarebefore cstat.076.294
  • lexmark c6160 firmwarebefore cstpp.076.294

Same product

lexmark: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-23560In certain Lexmark products through 2023-01-12, SSRF can occur because of a lack of input validation.
    43Plan
  • CVE-2021-44735Embedded web server command injection vulnerability in Lexmark devices through 2021-12-07.
    41Plan
  • CVE-2021-44734Embedded web server input sanitization vulnerability in Lexmark devices through 2021-12-07, which can which can lead to remote code executio
    41Plan
  • CVE-2021-44738Buffer overflow vulnerability has been identified in Lexmark devices through 2021-12-07 in postscript interpreter.
    40Plan
  • CVE-2023-22960Lexmark products through 2023-01-10 have Improper Control of Interaction Frequency.
    38Monitor
  • CVE-2022-29850Various Lexmark products through 2022-04-27 allow an attacker who has already compromised an affected Lexmark device to maintain persistence
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records