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

> A local attacker can execute arbitrary code by providing crafted executable files to the osslsigncode tool.

- **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:** 3 Jul 2023
- **Updated:** 30 Dec 2025
- **Also known as:** DEBIAN-CVE-2023-36377, DLA-3693-1, DLA-4426-1, GHSA-hgrq-rjwf-5f46, UBUNTU-CVE-2023-36377

## What is CVE-2023-36377?

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

### Official description

Buffer Overflow vulnerability in mtrojnar osslsigncode v.2.3 and before allows a local attacker to execute arbitrary code via a crafted .exe, .sys, and .dll files.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Osslsigncode Project Osslsigncode.

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

Upgrade to a fixed version.

## Is CVE-2023-36377 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-70888](https://insights.sbomify.com/CVE-2025-70888/): Privilege escalation in n/a (critical 9.8)
- [CVE-2026-39853](https://insights.sbomify.com/CVE-2026-39853/): osslsigncode has a Stack Buffer Overflow via Unbounded Digest Copy During Signature Verification (high 7.8)
- [CVE-2026-39855](https://insights.sbomify.com/CVE-2026-39855/): osslsigncode has an Integer Underflow in PE Page Hash Calculation Can Cause Out-of-Bounds Read (medium 5.5)
- [CVE-2026-39856](https://insights.sbomify.com/CVE-2026-39856/): osslsigncode has an Out-of-Bounds Read via Unvalidated Section Bounds in PE Page Hash Calculation (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36377 is a high-severity memory corruption vulnerability in n/a, published on 3 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36377 in the wild and no public exploit code.

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

## Sources

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

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