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

> A buffer overflow in the Codedoc library allows attackers to cause a denial of service via a specific component.

- **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:** No
- **Published:** 15 Aug 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-ph58-3r8h-4mqg

## What is CVE-2023-38850?

CVE-2023-38850 is a medium-severity memory corruption vulnerability in n/a, published on 15 Aug 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

Buffer Overflow vulnerability in Michaelrsweet codedoc v.3.7 allows an attacker to cause a denial of service via the codedoc.c:1742 comppnent.

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

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

It affects 1 product.


Products: Msweet Codedoc.

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

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

## Is CVE-2023-38850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38850 is a medium-severity memory corruption vulnerability in n/a, published on 15 Aug 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-38850 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-38850/ (Markdown: https://insights.sbomify.com/CVE-2023-38850/index.md)
```

## Sources

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

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