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.
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Varnish_cache | Varnish-cache | 6.1.0 (including) | 6.2.2 (excluding) |
| Varnish_cache | Varnish-cache | 6.3.0 (including) | 6.3.1 (excluding) |
| Varnish_cache | Varnish-software | 6.0.0 (including) | 6.0.5 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | varnish:6-8030020200530080205.30b713e6 | * |
| Varnish | Ubuntu | bionic | * |
| Varnish | Ubuntu | eoan | * |
| Varnish | Ubuntu | focal | * |
| Varnish | Ubuntu | trusty | * |
| Varnish | Ubuntu | xenial | * |
Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing. For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.