# CVE-2019-9933: Memory corruption in n/a

> A buffer overflow in Lexmark products allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7cq9-564p-27wv

## What is CVE-2019-9933?

CVE-2019-9933 is a critical memory corruption vulnerability in n/a, published on 28 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Various Lexmark products have a Buffer Overflow (issue 3 of 3).

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-9933?

It affects 71 products.


Products: Lexmark 6500e Firmware, Lexmark C734 Firmware, Lexmark C736 Firmware, Lexmark C746 Firmware, Lexmark C748 Firmware, Lexmark C792 Firmware, Lexmark C925 Firmware, Lexmark C950 Firmware, Lexmark Cs31x Firmware, Lexmark Cs41x Firmware, Lexmark Cs748 Firmware, Lexmark Cs796 Firmware, Lexmark Cx310 Firmware, Lexmark E46x Firmware, Lexmark M1140 Firmware, Lexmark M1145 Firmware, Lexmark M3150dn Firmware, Lexmark M5155 Firmware, Lexmark M5163 Firmware, Lexmark M5163dn Firmware and 51 more.

## How do I fix CVE-2019-9933?

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

## Is CVE-2019-9933 being exploited?

There is no known exploitation of CVE-2019-9933 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-10058](https://insights.sbomify.com/CVE-2019-10058/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9933 and fix it if it is affected.

What it is: CVE-2019-9933 is a critical memory corruption vulnerability in n/a, published on 28 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9933 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-2019-9933/ (Markdown: https://insights.sbomify.com/CVE-2019-9933/index.md)
```

## Sources

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

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