# CVE-2020-29540: Server-side request forgery in n/a

> Attackers can use the Systran Pure Neural Server as a proxy to launch Denial-of-Service attacks against arbitrary internal or external hosts via the Translation API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 8 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q663-qwpj-9w6q

## What is CVE-2020-29540?

CVE-2020-29540 is a high-severity server-side request forgery vulnerability in n/a, published on 8 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

API calls in the Translation API feature in Systran Pure Neural Server before 9.7.0 allow a threat actor to use the Systran Pure Neural Server as a Denial-of-Service proxy by sending a large amount of translation requests to a destination host on any given TCP port regardless of whether a web service is running on the destination port.

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

It affects 1 product.


Products: Systransoft Pure Neural Server.

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

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

## Is CVE-2020-29540 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-29539](https://insights.sbomify.com/CVE-2020-29539/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29540 is a high-severity server-side request forgery vulnerability in n/a, published on 8 Dec 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-29540 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-29540/ (Markdown: https://insights.sbomify.com/CVE-2020-29540/index.md)
```

## Sources

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

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