LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20637: An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6...

An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connection workspace, such as data structures associated with previous requests within this connection or VCL-related temporary headers.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Varnish Cache could accidentally expose leftover internal request data when handling multiple requests on the same client connection. The disclosed data may include temporary headers or request-related structures. This is an information disclosure issue, not a confirmed remote code execution issue in the provided sources. Exposure is most likely where affected Varnish Cache versions front web applications or APIs and process repeated client requests over persistent connections. The source bundle does not identify specific downstream products or packaged versions beyond Varnish and openSUSE advisories. Treat this as a medium-priority confidentiality risk for environments using Varnish at the web edge. Patch during the next security maintenance window, sooner for authenticated or sensitive services. There is no provided evidence of active exploitation. Mitigation focus: Upgrade Varnish Cache to 6.0.5 LTS, 6.2.2, 6.3.1, or a later fixed release.; Apply relevant distribution security updates, including the referenced openSUSE advisories where applicable.; Prioritize internet-facing Varnish deployments and systems fronting authenticated applications or APIs..

Prepared

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.

cve · low confidence lookup

CVE-2019-20637 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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