LiveActive security incident?Get immediate response
CVE Record

CVE-2017-7468: In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if t...

In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some curl/libcurl versions could reuse an old TLS session after the client certificate changed. A server might then rely on the previous identity instead of checking the new certificate. This is a medium-risk authentication correctness flaw, mainly relevant where client certificates are used for access control.

Executive priority

Treat as a targeted medium-priority fix. It is not presented as actively exploited, but it can weaken certificate-based authentication in affected deployments. Prioritize systems where client certificates gate privileged or sensitive access.

Technical view

CVE-2017-7468 is a CWE-295 issue in curl/libcurl described for 7.52.0 through 7.53.1. libcurl could resume TLS sessions despite a changed client certificate, allowing server-side resume behavior to associate the connection with an earlier identity. CVSS v3.0 is 4.8 with high attack complexity and low confidentiality/integrity impact.

Likely exposure

Exposure is most likely in applications or automation using affected curl/libcurl with TLS client certificates and session resumption. Environments not using client certificates are less likely to be meaningfully exposed. The bundle has inconsistent affected-version metadata, so validate against the curl and distribution advisories.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Abuse would depend on a specific client-certificate change scenario and server behavior during TLS session resumption. The CVSS vector marks attack complexity high.

Researcher notes

The bundle describes versions 7.52.0 through 7.53.1, while its affected entry lists curl 7.54.0. Treat that as incomplete or conflicting evidence and verify directly against curl and OS vendor advisories before closing findings.

Mitigation direction

  • Inventory curl and libcurl versions in systems, containers, and embedded packages.
  • Check curl and distribution advisories for the corrected package version.
  • Prioritize upgrades where client certificates protect sensitive services.
  • Confirm distro backports rather than relying only on upstream version strings.
  • Review TLS client-certificate workflows that reuse connections or sessions.

Validation and detection

  • Identify applications linked against libcurl, not only the curl CLI.
  • Check whether affected hosts use TLS client certificates for authentication.
  • Compare installed packages with vendor advisory status and changelog entries.
  • Verify scanners account for distribution backported fixes.
  • Document any version-range discrepancy found during validation.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-295: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-7468 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 3.0MediumCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N2.22.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.8Medium
CVSS 3.0 vector shape for CVE-2017-7468Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
[UNKNOWN]curlcurl 7.54.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.