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

> A buffer overflow in SwiftNIO allows attackers to execute arbitrary code or cause denial of service via improved size validation fixes.

- **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:** 11 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rx5q-753m-6mmq

## What is CVE-2018-4281?

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

### Official description

In SwiftNIO before 1.8.0, a buffer overflow was addressed with improved size validation.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Apple Swiftnio.

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

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

## Is CVE-2018-4281 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-3215](https://insights.sbomify.com/CVE-2022-3215/): SwiftNIO vulnerable to Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') (high 7.5)
- [CVE-2026-43678](https://insights.sbomify.com/CVE-2026-43678/): Denial of service in swift-nio (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-4281 is a critical memory corruption vulnerability in n/a, published on 11 Jan 2019. 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-4281 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-4281/ (Markdown: https://insights.sbomify.com/CVE-2018-4281/index.md)
```

## Sources

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

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