# CVE-2023-50735: A vulnerability has been identified in the PostScript interpreter in various Lexmark devices.

> Heap corruption in Lexmark PostScript interpreter allows attackers to execute arbitrary code on affected devices.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 Feb 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-xjjp-35cq-88wh

## What is CVE-2023-50735?

CVE-2023-50735 is a critical memory corruption vulnerability in Lexmark various, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap corruption vulnerability has been identified in PostScript interpreter in various Lexmark devices. The vulnerability can be leveraged by an attacker to execute arbitrary code.

Weakness: CWE-465

## Which versions are affected by CVE-2023-50735?


## How do I fix CVE-2023-50735?

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

## Is CVE-2023-50735 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50735 and fix it if it is affected.

What it is: CVE-2023-50735 is a critical memory corruption vulnerability in Lexmark various, published on 28 Feb 2024. 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-2023-50735 in the wild and no public exploit code.

Affected product: Lexmark various. 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-2023-50735/ (Markdown: https://insights.sbomify.com/CVE-2023-50735/index.md)
```

## Sources

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

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