usn-5474-1
Vulnerability from osv_ubuntu
It was dicovered that Varnish Cache did not clear a pointer between the handling of one client request and the next request within the same connection. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2019-20637)
It was discovered that Varnish Cache could have an assertion failure when a TLS termination proxy uses PROXY version 2. A remote attacker could possibly use this issue to restart the daemon and cause a performance loss. (CVE-2020-11653)
It was discovered that Varnish Cache allowed request smuggling and VCL authorization bypass via a large Content-Length header for a POST request. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2021-36740)
It was discovered that Varnish Cache allowed request smuggling for HTTP/1 connections. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2022-23959)
{
"affected": [
{
"database_specific": {
"cves_map": {
"cves": [
{
"id": "CVE-2019-20637",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2022-23959",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
}
],
"ecosystem": "Ubuntu:18.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libvarnishapi1",
"binary_version": "5.2.1-1ubuntu0.1"
},
{
"binary_name": "varnish",
"binary_version": "5.2.1-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "varnish",
"purl": "pkg:deb/ubuntu/varnish@5.2.1-1ubuntu0.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.2.1-1ubuntu0.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-7.1",
"5.2.1-1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [
{
"id": "CVE-2019-20637",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2020-11653",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "low",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2021-36740",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
},
{
"id": "CVE-2022-23959",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
}
],
"ecosystem": "Ubuntu:20.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libvarnishapi2",
"binary_version": "6.2.1-2ubuntu0.1"
},
{
"binary_name": "varnish",
"binary_version": "6.2.1-2ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "varnish",
"purl": "pkg:deb/ubuntu/varnish@6.2.1-2ubuntu0.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.2.1-2ubuntu0.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.1.1-1",
"6.2.1-2"
]
},
{
"database_specific": {
"cves_map": {
"cves": [
{
"id": "CVE-2022-23959",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
]
}
],
"ecosystem": "Ubuntu:22.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libvarnishapi2",
"binary_version": "6.6.1-1ubuntu0.2"
},
{
"binary_name": "varnish",
"binary_version": "6.6.1-1ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "varnish",
"purl": "pkg:deb/ubuntu/varnish@6.6.1-1ubuntu0.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.6.1-1ubuntu0.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.2-1",
"6.6.1-1"
]
}
],
"aliases": [],
"details": "It was dicovered that Varnish Cache did not clear a pointer between the\nhandling of one client request and the next request within the same connection.\nA remote attacker could possibly use this issue to obtain sensitive\ninformation. (CVE-2019-20637)\n\nIt was discovered that Varnish Cache could have an assertion failure when a\nTLS termination proxy uses PROXY version 2. A remote attacker could possibly\nuse this issue to restart the daemon and cause a performance loss.\n(CVE-2020-11653)\n\nIt was discovered that Varnish Cache allowed request smuggling and VCL\nauthorization bypass via a large Content-Length header for a POST\nrequest. A remote attacker could possibly use this issue to obtain sensitive\ninformation. (CVE-2021-36740)\n\nIt was discovered that Varnish Cache allowed request smuggling for HTTP/1\nconnections. A remote attacker could possibly use this issue to obtain\nsensitive information. (CVE-2022-23959)\n",
"id": "USN-5474-1",
"modified": "2026-04-27T14:11:28Z",
"published": "2022-06-08T19:20:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-5474-1"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2019-20637"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-11653"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2021-36740"
},
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2022-23959"
}
],
"related": [],
"schema_version": "1.7.0",
"summary": "varnish vulnerabilities",
"upstream": [
"UBUNTU-CVE-2019-20637",
"UBUNTU-CVE-2020-11653",
"UBUNTU-CVE-2021-36740",
"UBUNTU-CVE-2022-23959"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.