LiveActive security incident?Get immediate response
CVE Record

CVE-2016-8620: The 'globbing' feature in curl before version 7.51.0 has a flaw that leads to integer overflow and out-of-b...

The 'globbing' feature in curl before version 7.51.0 has a flaw that leads to integer overflow and out-of-bounds read via user controlled input.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older curl versions could mishandle specially crafted URL globbing input, causing an integer overflow and out-of-bounds read. For executives, this is a moderate supply-chain and infrastructure hygiene issue: curl is widely embedded, but the supplied sources do not show confirmed active exploitation.

Executive priority

Treat as a moderate patch-management priority, especially for internet-facing automation, appliances, and container images. It does not warrant emergency response from the supplied evidence, but curl’s ubiquity makes delayed remediation risky in unmanaged environments.

Technical view

The flaw is in curl URL globbing before 7.51.0. User-controlled globbing input can trigger integer overflow and out-of-bounds read behavior. The CVE is scored CVSS 3.0 6.5 with network attack vector, low complexity, no privileges, no user interaction, and limited confidentiality and integrity impact.

Likely exposure

Exposure is most likely where systems, scripts, or bundled applications use curl/libcurl versions before 7.51.0 and pass untrusted input into URL globbing behavior. The supplied data does not identify specific downstream application exposure beyond curl and vendor advisories.

Exploitation context

The source bundle does not include KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote, low-complexity conditions without privileges or user interaction, but the available sources do not provide exploitation details or real-world incident evidence.

Researcher notes

Primary uncertainty is practical exploitability in real deployments. The issue requires curl globbing with user-controlled input, but the supplied sources do not describe exploit prevalence, affected application patterns, or proof of active exploitation. Validate exposure through version inventory and data-flow review.

Mitigation direction

  • Identify curl and libcurl versions across servers, containers, appliances, and vendor software.
  • Upgrade to vendor-supported packages containing the upstream curl fix for CVE-2016-8620.
  • Review OS vendor advisories from Red Hat, Gentoo, Oracle, and other relevant suppliers.
  • Avoid passing untrusted input into curl URL globbing features until patched.
  • Track vendor guidance where curl is embedded inside third-party products.

Validation and detection

  • Confirm deployed curl/libcurl versions are not before 7.51.0 or are vendor-backported fixes.
  • Check package changelogs or advisories for CVE-2016-8620 remediation.
  • Inventory scripts and services that build curl URLs from external input.
  • Validate container images and appliance firmware include patched curl packages.
  • Document any vendor-dependent exceptions and remediation owners.
Prepared
Confidence
medium
Sources
6

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-120: 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-2016-8620 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
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/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
6Source 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
6.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2016-8620Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/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
The Curl Projectcurl7.51.0Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.