dbcve.org
FedoraOperating system · Fedoraproject

CVE-2015-3148

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-24
Fix available
A fix is available. Upgrade to after 7.5.3.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
cURL and libcurl 7.10.6 through 7.41.0 do not properly re-use authenticated Negotiate connections, which allows remote attackers to connect as other users via a request.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

libcurl 7.10.6 through 7.41.0 does not properly re-use authenticated Negotiate (GSSAPI/Kerberos) connections. When a connection authenticated with Negotiate is available in the connection pool, subsequent requests may incorrectly re-use that connection for different users, allowing an attacker to inherit the authenticated session of a previous user.

MitigationUpgrade libcurl to version 7.42.0 or later, which contains the fix for proper Negotiate connection re-use validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 21= 22
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 14.10= 15.04
Debian LinuxOperating system
Affected:= 7.0
CurlApplication
Affected:= 7.10.6= 7.10.7= 7.10.8= 7.11.0= 7.11.1= 7.11.2= 7.12.0= 7.12.1= 7.12.2= 7.12.3= 7.13.0= 7.13.1
Mac Os XOperating system
Affected:= 10.10.0= 10.10.1= 10.10.2= 10.10.3= 10.10.4
LibcurlApplication
Affected:= 7.10.6= 7.10.7= 7.10.8= 7.11.0= 7.11.1= 7.11.2= 7.12.0= 7.12.1= 7.12.2= 7.12.3= 7.13.0= 7.13.1
System Management HomepageApplication
Affected:<= 7.5.3.1
OpensuseOperating system
Affected:= 13.1= 13.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed libcurl version
    Run 'curl --version' or check the libcurl library file version (e.g., 'dpkg -l libcurl3' on Debian/Ubuntu, 'rpm -q libcurl' on RHEL/Fedora, or examine the shared library file)
    Affected if The version is 7.10.6 through 7.41.0 inclusive
  2. Confirm Negotiate (GSSAPI/Kerberos) authentication is in use
    Review application configuration or code to determine if curl is configured to use Negotiate, GSSAPI, or Kerberos authentication methods (typically via CURLOPT_GSSAPI_DELEGATION, --negotiate, or similar options)
    Affected if Negotiate/GSSAPI/Kerberos authentication is enabled and used with libcurl
  3. Verify HTTP keep-alive connection pooling is active
    Check if the application uses HTTP keep-alive (default behavior) which enables connection re-use via the connection pool; this can be confirmed by inspecting curl_easy_setopt calls for CURLOPT_FORBID_REUSE or observing persistent connections in network traffic
    Affected if HTTP keep-alive is enabled (default) allowing connection pooling to occur, combined with Negotiate authentication

If your libcurl version falls within 7.10.6 to 7.41.0 AND you use Negotiate/GSSAPI/Kerberos authentication with HTTP keep-alive enabled, your environment is affected by this flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.5.3.1
Interim mitigation

Upgrade libcurl to version 7.42.0 or later, which contains the fix for proper Negotiate connection re-use validation.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3148 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data