# CVE-2018-19571: Server-side request forgery in n/a

> Attackers can exploit a Server-Side Request Forgery vulnerability in GitLab webhooks to access internal resources or bypass security controls.

- **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:** 10 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hrrx-p8r8-gj4g

## What is CVE-2018-19571?

CVE-2018-19571 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 10 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability in webhooks.

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

## Which versions are affected by CVE-2018-19571?

It affects 1 product.


Products: Gitlab Gitlab.

## How do I fix CVE-2018-19571?

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

## Is CVE-2018-19571 being exploited?

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

Public exploit code:

- GitLab 11.4.7 RCE exploit with different reverse shells. CVE-2018-19571 + CVE-2018-19585 (github_poc): https://github.com/Algafix/gitlab-RCE-11.4.7
- GitLab 11.4.7 - Remote Code Execution (Authenticated) (1) (exploitdb)
- GitLab 11.4.7 - RCE (Authenticated) (2) (exploitdb)
- Fixed version of the Python script to exploit CVE-2018-19571 and CVE-2018-19585 (GitLab 11.4.7 - Authenticated Remote Code Execution) that is available at https://www.exploit-db.com/exploits/49263 (Python 3.9). (github_poc): https://github.com/xenophil90/edb-49263-fixed
- Demonstration of CVE-2018-19571: GitLab SSRF CVE (github_poc): https://github.com/CS4239-U6/gitlab-ssrf

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19571 and fix it if it is affected.

What it is: CVE-2018-19571 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 10 Jul 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-2018-19571 in the wild and no public exploit code.

Affected product: Gitlab Gitlab. 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-2018-19571/ (Markdown: https://insights.sbomify.com/CVE-2018-19571/index.md)
```

## Sources

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

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