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

> A heap-use-after-free in jbig2enc allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Nov 2023
- **Updated:** 4 Sep 2024
- **Also known as:** DEBIAN-CVE-2023-46362, GHSA-f4hj-7928-3pr9, UBUNTU-CVE-2023-46362

## What is CVE-2023-46362?

CVE-2023-46362 is a medium-severity use after free vulnerability in n/a, published on 8 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

jbig2enc v0.28 was discovered to contain a heap-use-after-free via jbig2enc_auto_threshold_using_hash in src/jbig2enc.cc.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Jbig2enc Project Jbig2enc.

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

Upgrade to a fixed version.

## Is CVE-2023-46362 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11230](https://insights.sbomify.com/CVE-2018-11230/): Use after free in n/a (high 8.8)
- [CVE-2023-46363](https://insights.sbomify.com/CVE-2023-46363/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46362 is a medium-severity use after free vulnerability in n/a, published on 8 Nov 2023. It can only be exploited from the same machine or local network, 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-46362 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-46362/ (Markdown: https://insights.sbomify.com/CVE-2023-46362/index.md)
```

## Sources

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

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