# CVE-2017-2628: Auth bypass in curl

> A backporting error in Red Hat's curl package failed to properly disable GSSAPI, potentially allowing authentication bypass in HTTP Negotiate scenarios.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9v4c-xqrp-4vv9, RHSA-2017:0847

## What is CVE-2017-2628?

CVE-2017-2628 is a critical authentication bypass vulnerability in Haxx Curl, published on 12 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

curl, as shipped in Red Hat Enterprise Linux 6 before version 7.19.7-53, did not correctly backport the fix for CVE-2015-3148 because it did not reflect the fact that the HAVE_GSSAPI define was meanwhile substituted by USE_HTTP_NEGOTIATE. This issue was introduced in RHEL 6.7 and affects RHEL 6 curl only.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl` | Red Hat:enterprise_linux:6::client | All versions | 0:7.19.7-53.el6_9 |
| `curl-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:7.19.7-53.el6_9 |
| `libcurl` | Red Hat:enterprise_linux:6::client | All versions | 0:7.19.7-53.el6_9 |
| `libcurl-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:7.19.7-53.el6_9 |
| `curl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:7.19.7-53.el6_9 |
| `curl-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:7.19.7-53.el6_9 |
| `libcurl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:7.19.7-53.el6_9 |
| `libcurl-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:7.19.7-53.el6_9 |
| `curl` | Red Hat:enterprise_linux:6::server | All versions | 0:7.19.7-53.el6_9 |
| `curl-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:7.19.7-53.el6_9 |
| `libcurl` | Red Hat:enterprise_linux:6::server | All versions | 0:7.19.7-53.el6_9 |
| `libcurl-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:7.19.7-53.el6_9 |
| `curl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:7.19.7-53.el6_9 |
| `curl-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:7.19.7-53.el6_9 |
| `libcurl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:7.19.7-53.el6_9 |
| `libcurl-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:7.19.7-53.el6_9 |

Products: Haxx Curl.

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

Apply the vendor's patch.

## Is CVE-2017-2628 being exploited?

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

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2628 is a critical authentication bypass vulnerability in Haxx Curl, published on 12 Mar 2018. 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-2628 in the wild and no public exploit code.

Affected product: Haxx Curl. 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-2628/ (Markdown: https://insights.sbomify.com/CVE-2017-2628/index.md)
```

## Sources

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

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