# CVE-2021-44737: Path traversal in n/a

> Attackers can exploit a PJL directory traversal flaw in Lexmark devices to overwrite internal configuration files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9qpx-hw6q-qw9h

## What is CVE-2021-44737?

CVE-2021-44737 is a high-severity path traversal vulnerability in n/a, published on 20 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-44737?

It affects 234 products.


Products: Lexmark 6500e Firmware, Lexmark B2236 Firmware, Lexmark B2338 Firmware, Lexmark B2442 Firmware, Lexmark B2546 Firmware, Lexmark B2650 Firmware, Lexmark B2865 Firmware, Lexmark B3340 Firmware, Lexmark B3442 Firmware, Lexmark C2132 Firmware, Lexmark C2240 Firmware, Lexmark C2325 Firmware, Lexmark C2326 Firmware, Lexmark C2425 Firmware, Lexmark C2535 Firmware, Lexmark C3224 Firmware, Lexmark C3326 Firmware, Lexmark C3426 Firmware, Lexmark C4150 Firmware, Lexmark C6160 Firmware and 214 more.

## How do I fix CVE-2021-44737?

No fix has been published for CVE-2021-44737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-44737 being exploited?

There is no known exploitation of CVE-2021-44737 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-44734](https://insights.sbomify.com/CVE-2021-44734/): Code injection in n/a (critical 9.8)
- [CVE-2021-44738](https://insights.sbomify.com/CVE-2021-44738/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9930](https://insights.sbomify.com/CVE-2019-9930/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-9932](https://insights.sbomify.com/CVE-2019-9932/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9933](https://insights.sbomify.com/CVE-2019-9933/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44737 and fix it if it is affected.

What it is: CVE-2021-44737 is a high-severity path traversal vulnerability in n/a, published on 20 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-44737 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-44737/ (Markdown: https://insights.sbomify.com/CVE-2021-44737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-44737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-44737
- OSV: https://osv.dev/vulnerability/CVE-2021-44737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-44737/
Summaries are generated and may contain mistakes; the official description above is the record.
