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

> An attacker can exploit an SSRF vulnerability in the fetch API to proxy internal traffic or serve malicious content, bypassing firewalls and hijacking user trust.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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:** 26 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c34j-6jv7-qfwj

## What is CVE-2019-13020?

CVE-2019-13020 is a critical server-side request forgery vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The fetch API in Tightrope Media Carousel before 7.1.3 has CarouselAPI/v0/fetch?url= SSRF. This has two potential areas for abuse. First, a specially crafted URL could be used in a phishing attack to hijack the trust the user and the browser have with the website and could serve malicious content from a third-party attacker-controlled system. Second, arguably more severe, is the potential for an attacker to circumvent firewall controls, by proxying traffic, unauthenticated, into the internal network from the internet.

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

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

It affects 1 product.


Products: Trms Tightrope Media Carousel.

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

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

## Is CVE-2019-13020 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13020 is a critical server-side request forgery vulnerability in n/a, published on 26 Aug 2019. 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-2019-13020 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-13020/ (Markdown: https://insights.sbomify.com/CVE-2019-13020/index.md)
```

## Sources

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

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