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

> Out-of-bounds memory access in exfatprogs allows attackers to execute arbitrary code or cause denial of service via crafted exFAT filesystems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 28 Oct 2023
- **Updated:** 5 Sep 2024
- **Also known as:** ALSA-2024:2437, CLSA-2026-1779895093, DEBIAN-CVE-2023-45897, DLA-3861-1, GHSA-5qgg-v88w-rgh6, MGASA-2024-0166, RHSA-2024:2437, RLSA-2024:2437, SUSE-SU-2023:4449-1, UBUNTU-CVE-2023-45897, USN-6970-1

## What is CVE-2023-45897?

CVE-2023-45897 is a medium-severity memory corruption vulnerability in n/a, published on 28 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

exfatprogs before 1.2.2 allows out-of-bounds memory access, such as in read_file_dentry_set.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `exfatprogs` | AlmaLinux:9 | All versions | 1.2.2-2.el9 |
| `exfatprogs` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.2.2-2.el9 |
| `exfatprogs-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.2.2-2.el9 |
| `exfatprogs-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.2.2-2.el9 |
| `exfatprogs` | Rocky Linux:9 | All versions | 0:1.2.2-2.el9 |
| `exfatprogs` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.0.4-150300.3.12.1 |
| `exfatprogs` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 1.0.4-150300.3.12.1 |
| `exfatprogs` | openSUSE:Leap 15.4 | All versions | 1.0.4-150300.3.12.1 |
| `exfatprogs` | openSUSE:Leap 15.5 | All versions | 1.0.4-150300.3.12.1 |

Products: Namjaejeon Exfatprogs.

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

Upgrade to a fixed version.

## Is CVE-2023-45897 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45897 is a medium-severity memory corruption vulnerability in n/a, published on 28 Oct 2023. 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-45897 exists.

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-2023-45897/ (Markdown: https://insights.sbomify.com/CVE-2023-45897/index.md)
```

## Sources

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

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