# CVE-2018-19585: Other in n/a

> Attackers can inject CRLF characters in Git protocol mirroring, potentially manipulating logs or responses, requiring GitLab upgrades.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 17 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-49rg-2gmx-qjmr

## What is CVE-2018-19585?

CVE-2018-19585 is a high-severity vulnerability in Gitlab Gitlab, published on 17 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GitLab CE/EE versions 8.18 up to 11.x before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1 have CRLF Injection in Project Mirroring when using the Git protocol.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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

It affects 1 product.


Products: Gitlab Gitlab.

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

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

## Is CVE-2018-19585 being exploited?

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

Public exploit code:

- GitLab 11.4.7 - Remote Code Execution (Authenticated) (1) (exploitdb)
- GitLab 11.4.7 - RCE (Authenticated) (2) (exploitdb)

## 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-19585 and fix it if it is affected.

What it is: CVE-2018-19585 is a high-severity vulnerability in Gitlab Gitlab, published on 17 May 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-2018-19585 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-19585/ (Markdown: https://insights.sbomify.com/CVE-2018-19585/index.md)
```

## Sources

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

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