# CVE-2019-15033: Server-side request forgery in n/a

> Authenticated attackers can exploit a remote link feature to perform Server-Side Request Forgery against internal network resources.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 19 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-47g3-vpfv-8v8q

## What is CVE-2019-15033?

CVE-2019-15033 is a high-severity server-side request forgery vulnerability in n/a, published on 19 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pydio 6.0.8 allows Authenticated SSRF during a Remote Link Feature download. An attacker can specify an intranet address in the file parameter to index.php, when sending a file to a remote server, as demonstrated by the file=http%3A%2F%2F192.168.1.2 substring.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-15033?

It affects 1 product.


Products: Pydio Pydio.

## How do I fix CVE-2019-15033?

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

## Is CVE-2019-15033 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4267](https://insights.sbomify.com/CVE-2013-4267/): Command injection in Ajaxeplorer (critical 9.8)
- [CVE-2019-9642](https://insights.sbomify.com/CVE-2019-9642/): Code injection in n/a (critical 9.8)
- [CVE-2018-20718](https://insights.sbomify.com/CVE-2018-20718/): Deserialization in n/a (critical 9.8)
- [CVE-2015-3431](https://insights.sbomify.com/CVE-2015-3431/): Command injection in n/a (critical 9.8)
- [CVE-2019-20452](https://insights.sbomify.com/CVE-2019-20452/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15033 and fix it if it is affected.

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

## Sources

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

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