# CVE-2016-5325: Other in n/a

> Remote attackers can inject HTTP headers and split responses via the writeHead reason argument in Node.js.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-5325, GHSA-qpf8-fqrf-8p2h, UBUNTU-CVE-2016-5325

## What is CVE-2016-5325?

CVE-2016-5325 is a medium-severity vulnerability in Nodejs Node.js, published on 10 Oct 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CRLF injection vulnerability in the ServerResponse#writeHead function in Node.js 0.10.x before 0.10.47, 0.12.x before 0.12.16, 4.x before 4.6.0, and 6.x before 6.7.0 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the reason argument.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2016-5325?

It affects 2 products.


Products: Nodejs Node.js, Suse Linux Enterprise.

## How do I fix CVE-2016-5325?

Upgrade to a fixed version.

## Is CVE-2016-5325 being exploited?

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5325 and fix it if it is affected.

What it is: CVE-2016-5325 is a medium-severity vulnerability in Nodejs Node.js, published on 10 Oct 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-5325 in the wild and no public exploit code.

Affected product: Nodejs Node.js. 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-2016-5325/ (Markdown: https://insights.sbomify.com/CVE-2016-5325/index.md)
```

## Sources

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

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