Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 8.03% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2018
CVE-2018-1000007High confidence
Affected product: security vulnerability
Unknown · Unknown
9.8CriticalCVSS 3.1
Within 72 hours
Patch availableCritical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.58.0-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian bookwormbookworm · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.58.0-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian forkyforky · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.58.0-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian sidsid · source | curl | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.58.0-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
Direct vendor intelligence
1 current · 1 archivedAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2018-1000007 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2018-1000007
The vendor explicitly states that these products are not affected by this CVE.
- curl as component of SUSE CaaS Platform 4.0
- libcurl-devel as component of SUSE CaaS Platform 4.0
- libcurl4 as component of SUSE CaaS Platform 4.0
- libcurl4-32bit as component of SUSE CaaS Platform 4.0
- curl as component of SUSE Enterprise Storage 6
- curl as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- libcurl4 as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- curl as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
- libcurl-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
- libcurl4 as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
- libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
- Summary
- libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2018-1000007 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycurl: HTTP authentication leak in redirectsNo longer in the provider’s current catalogue
The vendor explicitly identifies these products as affected by this CVE.
- rh-dotnetcore10-curl.src as a component of .NET Core 1.0 on Red Hat Enterprise Linux
- rh-dotnetcore11-curl.src as a component of .NET Core 1.1 on Red Hat Enterprise Linux
- rh-dotnet20-curl.src as a component of .NET Core 2.0 on Red Hat Enterprise Linux
- rh-dotnet21-curl.src as a component of .NET Core 2.1 on Red Hat Enterprise Linux
- rh-dotnet21-libcurl as a component of .NET Core 2.1 on Red Hat Enterprise Linux
- rh-dotnet21-libcurl-devel as a component of .NET Core 2.1 on Red Hat Enterprise Linux
- curl.src as a component of Red Hat Enterprise Linux 5
- curl as a component of Red Hat Enterprise Linux 6
- curl.src as a component of Red Hat Enterprise Linux 6
- libcurl as a component of Red Hat Enterprise Linux 6
- libcurl-devel as a component of Red Hat Enterprise Linux 6
- Summary
- It was found that curl and libcurl might send their Authentication header to a third party HTTP server upon receiving an HTTP REDIRECT reply. This could leak authentication token to external entities.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically.
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Patch available01
What, why and how
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
What
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.
What
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → vulnerable operation → obtain information outside the intended access boundary
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- n/a
- Action
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 24 Jan 2018 · Last source change 5 Aug 2024, 12:33 UTC · CWE not yet assigned
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2018-1778
Product sourceUnavailable
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification, affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2018-1000007 to advisory no longer present in the provider's current catalogue.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2018-1000007
- After
- advisory no longer present in the provider's current catalogue
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- n/a · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically.
- ENISA EUVD mappingEUVD-2018-1778 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2018-1778"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: curl.haxx.se/adv_2018-b3bf.html; added patch: oracle.com/cpuoct2019-5072832.html; removed vendor advisory: access.redhat.com/RHBA-2019:0327; removed vendor advisory: access.redhat.com/RHSA-2018:3157; 1 further additions; 7 further removals.curl.haxx.se ↗
- Before
- vendor advisory: access.redhat.com/RHBA-2019:0327 · vendor advisory: access.redhat.com/RHSA-2018:3157 · vendor advisory: access.redhat.com/RHSA-2018:3558 · 6 more references
- After
- patch: curl.haxx.se/adv_2018-b3bf.html · patch: oracle.com/cpuoct2019-5072832.html · remediation: curl.haxx.se/adv_2018-b3bf.html
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.curl.haxx.se ↗
- Before
- Awaiting fix
- After
- Patch available
- SeveritySeverity changed from Unknown to Critical.NIST NVD ↗
- Before
- Unknown
- After
- Critical
- CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).NIST NVD ↗
- Before
- not recorded
- After
- 9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.