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

> Remote attackers can inject HTTP headers and split responses in Huawei FusionAccess, potentially bypassing security controls.

- **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:** No
- **Published:** 7 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3q32-62v8-wp6j

## What is CVE-2016-6839?

CVE-2016-6839 is a medium-severity vulnerability in n/a, published on 7 Sep 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 Huawei FusionAccess before V100R006C00 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.

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

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

It affects 1 product.


Products: Huawei Fusionaccess.

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

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

## Is CVE-2016-6839 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9090](https://insights.sbomify.com/CVE-2020-9090/): Missing authorization in FusionAccess (high 7.8)
- [CVE-2015-7844](https://insights.sbomify.com/CVE-2015-7844/): Denial of service in FusionAccess V100R005C10,V100R005C20 (high 7.5)
- [CVE-2020-1825](https://insights.sbomify.com/CVE-2020-1825/): Denial of service in FusionAccess (medium 6.5)
- [CVE-2016-8779](https://insights.sbomify.com/CVE-2016-8779/): Other in FusionAccess FusionAccess V100R005C10, FusionAccess V100R005C20 (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6839 is a medium-severity vulnerability in n/a, published on 7 Sep 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-6839 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-2016-6839/ (Markdown: https://insights.sbomify.com/CVE-2016-6839/index.md)
```

## Sources

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

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