# CVE-2023-48024: Use after free in n/a

> A use-after-free vulnerability in Liblisp's hash_destroy function allows attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2023
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-h985-4pxm-24pr

## What is CVE-2023-48024?

CVE-2023-48024 is a medium-severity use after free vulnerability in n/a, published on 17 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Liblisp through commit 4c65969 was discovered to contain a use-after-free vulnerability in void hash_destroy(hash_table_t *h) at hash.c

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Howerj Liblisp.

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

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

## Is CVE-2023-48024 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-48025](https://insights.sbomify.com/CVE-2023-48025/): Memory corruption in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48024 is a medium-severity use after free vulnerability in n/a, published on 17 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-48024 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-48024/ (Markdown: https://insights.sbomify.com/CVE-2023-48024/index.md)
```

## Sources

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

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