# CVE-2018-11545: Memory corruption in n/a

> A heap-based buffer overflow in the md4c library allows attackers to execute arbitrary code or cause denial of service via crafted markdown input.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-78q4-2c8r-5ghp

## What is CVE-2018-11545?

CVE-2018-11545 is a critical memory corruption vulnerability in n/a, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

md4c 0.2.5 has a heap-based buffer overflow in md_merge_lines because md_is_link_label mishandles the case of a link label composed solely of backslash escapes.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-11545?

It affects 1 product.


Products: Md4c Project Md4c.

## How do I fix CVE-2018-11545?

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

## Is CVE-2018-11545 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11536](https://insights.sbomify.com/CVE-2018-11536/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-11546](https://insights.sbomify.com/CVE-2018-11546/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-11547](https://insights.sbomify.com/CVE-2018-11547/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-12112](https://insights.sbomify.com/CVE-2018-12112/): Memory corruption in n/a (high 7.8)
- [CVE-2020-26148](https://insights.sbomify.com/CVE-2020-26148/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11545 and fix it if it is affected.

What it is: CVE-2018-11545 is a critical memory corruption vulnerability in n/a, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11545 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-2018-11545/ (Markdown: https://insights.sbomify.com/CVE-2018-11545/index.md)
```

## Sources

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

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