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

> A buffer over-read in the PBC library allows attackers to cause denial of service or disclose sensitive memory contents via crafted PTYPE_ENUM messages.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rp4v-jwqp-68p6

## What is CVE-2018-14736?

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

### Official description

An issue was discovered in libpbc.a in cloudwu PBC through 2017-03-02. A buffer over-read can occur in pbc_wmessage_string in wmessage.c for PTYPE_ENUM.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Pbc Project Pbc.

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

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

## Is CVE-2018-14736 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14744](https://insights.sbomify.com/CVE-2018-14744/): Use after free in n/a (critical 9.8)
- [CVE-2018-12915](https://insights.sbomify.com/CVE-2018-12915/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-12916](https://insights.sbomify.com/CVE-2018-12916/): Null dereference in n/a (critical 9.8)
- [CVE-2018-12917](https://insights.sbomify.com/CVE-2018-12917/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-12918](https://insights.sbomify.com/CVE-2018-12918/): Null dereference in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14736 is a high-severity memory corruption vulnerability in n/a, published on 29 Jul 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-14736 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-14736/ (Markdown: https://insights.sbomify.com/CVE-2018-14736/index.md)
```

## Sources

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

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