# CVE-2017-6100: Server-side request forgery in n/a

> An attacker can force the TCPDF library to upload server files to an external FTP server, potentially exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-6100, GHSA-xv34-wq27-w2wm, MGASA-2017-0067, UBUNTU-CVE-2017-6100

## What is CVE-2017-6100?

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

### Official description

tcpdf before 6.2.0 uploads files from the server generating PDF-files to an external FTP.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2017-6100?

It affects 1 product.


Products: Tcpdf Project Tcpdf.

## How do I fix CVE-2017-6100?

Upgrade to a fixed version.

## Is CVE-2017-6100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-56521](https://insights.sbomify.com/CVE-2024-56521/): TCPDF missing certificate validation (critical 9.8)
- [CVE-2024-56519](https://insights.sbomify.com/CVE-2024-56519/): TCPDF lacks SVG sanitization (high 7.5)
- [CVE-2024-56522](https://insights.sbomify.com/CVE-2024-56522/): TCPDF has incorrect comparison (high 7.5)
- [CVE-2024-56527](https://insights.sbomify.com/CVE-2024-56527/): TCPDF missing character escape on error messages (high 7.5)
- [CVE-2024-22641](https://insights.sbomify.com/CVE-2024-22641/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6100 and fix it if it is affected.

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

## Sources

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

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