# CVE-2023-51257: Memory corruption in n/a

> A local attacker can execute arbitrary code via an invalid memory write in the Jasper image library.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-33325, AZL-34807, CLSA-2024-1723146304, CLSA-2025-1746187690, GHSA-c74w-77jp-9c48, SUSE-SU-2024:0240-1, SUSE-SU-2024:0241-1, UBUNTU-CVE-2023-51257, openSUSE-SU-2024:13576-1

## What is CVE-2023-51257?

CVE-2023-51257 is a high-severity memory corruption vulnerability in Jasper Project Jasper, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An invalid memory write issue in Jasper-Software Jasper v.4.1.1 and before allows a local attacker to execute arbitrary code.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jasper` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.0.14-150000.3.31.1 |
| `jasper` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 2.0.14-150000.3.31.1 |
| `jasper` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.900.14-195.37.1 |
| `jasper` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.900.14-195.37.1 |
| `jasper` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.900.14-195.37.1 |
| `jasper` | openSUSE:Leap 15.5 | All versions | 2.0.14-150000.3.31.1 |
| `jasper` | openSUSE:Tumbleweed | All versions | 4.1.2-1.1 |

Products: Jasper Project Jasper.

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

Apply the vendor's patch.

## Is CVE-2023-51257 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51257 exists.

## Other vulnerabilities in Jasper Project Jasper

- [CVE-2008-3522](https://insights.sbomify.com/CVE-2008-3522/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3520](https://insights.sbomify.com/CVE-2008-3520/): Integer overflow in n/a (critical 9.3)
- [CVE-2015-8751](https://insights.sbomify.com/CVE-2015-8751/): Integer overflow in n/a (high 8.8)
- [CVE-2016-8886](https://insights.sbomify.com/CVE-2016-8886/): Memory corruption in n/a (high 7.8)
- [CVE-2016-9387](https://insights.sbomify.com/CVE-2016-9387/): Integer overflow in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51257 is a high-severity memory corruption vulnerability in Jasper Project Jasper, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51257 exists.

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

## Sources

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

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