CVE Intelligence
Skip to main content
MEDIUM

CVE-2016-8624

CVE-2016-8624 Vulnerability Analysis & Exploit Intelligence

curl before version 7.51.0 doesn't parse the authority component of the URL correctly when the host name part ends with a '#' character, and could instead be tricked into connecting to a different host. This may have security implications if you for example use an URL parser that follows the RFC to check for allowed domains before using curl to request them.

Published Updated Sources: cvelistV5, redhat

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

6%

chance of exploitation in 30 days

Affects

the curl project

curl

CVSS base

5.3

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

the curl project

Products (1)

curl

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.3CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-20

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1562.003Impair Defenses: Impair Command History Logging
  • T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

References

12 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.