# CVE-2020-11703: Other in n/a

> Attackers can perform HTTP Response Splitting via the language parameter in ProVide FTP server, potentially manipulating client responses.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8qhf-pcp9-49xc

## What is CVE-2020-11703?

CVE-2020-11703 is a high-severity vulnerability in n/a, published on 12 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in ProVide (formerly zFTPServer) through 13.1. /ajax/GetInheritedProperties allows HTTP Response Splitting via the language parameter.

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

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

It affects 1 product.


Products: Provideserver Provide Ftp Server.

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

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

## Is CVE-2020-11703 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11705](https://insights.sbomify.com/CVE-2020-11705/): Path traversal in n/a (critical 9.8)
- [CVE-2020-11708](https://insights.sbomify.com/CVE-2020-11708/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-11701](https://insights.sbomify.com/CVE-2020-11701/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-11706](https://insights.sbomify.com/CVE-2020-11706/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-11707](https://insights.sbomify.com/CVE-2020-11707/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11703 is a high-severity vulnerability in n/a, published on 12 Apr 2020. 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-2020-11703 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-11703/ (Markdown: https://insights.sbomify.com/CVE-2020-11703/index.md)
```

## Sources

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

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