# CVE-2020-12855: Open redirect in n/a

> Authenticated attackers can inject Host headers to control 302 redirects, potentially enabling phishing or bypassing security controls in SecZetta NEProfile.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qqrr-xgq7-v24p

## What is CVE-2020-12855?

CVE-2020-12855 is a high-severity vulnerability in n/a, published on 26 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Host header injection vulnerability has been discovered in SecZetta NEProfile 3.3.11. Authenticated remote adversaries can poison this header resulting in an adversary controlling the execution flow for the 302 HTTP status.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-12855?

It affects 1 product.


Products: Seczetta Neprofile.

## How do I fix CVE-2020-12855?

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

## Is CVE-2020-12855 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12854](https://insights.sbomify.com/CVE-2020-12854/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12855 and fix it if it is affected.

What it is: CVE-2020-12855 is a high-severity vulnerability in n/a, published on 26 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12855 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-2020-12855/ (Markdown: https://insights.sbomify.com/CVE-2020-12855/index.md)
```

## Sources

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

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