rpm package
suse/squid&distro=SUSE Linux Enterprise Server for SAP Applications 12 SP2
pkg:rpm/suse/squid&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP2
Vulnerabilities (29)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2019-18679 | — | < 3.5.21-26.20.1 | 3.5.21-26.20.1 | Nov 26, 2019 | An issue was discovered in Squid 2.x, 3.x, and 4.x through 4.8. Due to incorrect data management, it is vulnerable to information disclosure when processing HTTP Digest Authentication. Nonce tokens contain the raw byte value of a pointer that sits within heap memory allocation. T | ||
| CVE-2019-12529 | — | < 3.5.21-26.17.1 | 3.5.21-26.17.1 | Jul 11, 2019 | An issue was discovered in Squid 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7. When Squid is configured to use Basic Authentication, the Proxy-Authorization header is parsed via uudecode. uudecode determines how many bytes will be decoded by iterating over the | ||
| CVE-2019-12525 | — | < 3.5.21-26.17.1 | 3.5.21-26.17.1 | Jul 11, 2019 | An issue was discovered in Squid 3.3.9 through 3.5.28 and 4.x through 4.7. When Squid is configured to use Digest authentication, it parses the header Proxy-Authorization. It searches for certain tokens such as domain, uri, and qop. Squid checks if this token's value starts with | ||
| CVE-2019-13345 | — | < 3.5.21-26.17.1 | 3.5.21-26.17.1 | Jul 5, 2019 | The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter. | ||
| CVE-2018-1000027 | — | < 3.5.21-26.6.1 | 3.5.21-26.6.1 | Feb 9, 2018 | The Squid Software Foundation Squid HTTP Caching Proxy version prior to version 4.0.23 contains a NULL Pointer Dereference vulnerability in HTTP Response X-Forwarded-For header processing that can result in Denial of Service to all clients of the proxy. This attack appear to be e | ||
| CVE-2018-1000024 | — | < 3.5.21-26.6.1 | 3.5.21-26.6.1 | Feb 9, 2018 | The Squid Software Foundation Squid HTTP Caching Proxy version 3.0 to 3.5.27, 4.0 to 4.0.22 contains a Incorrect Pointer Handling vulnerability in ESI Response Processing that can result in Denial of Service for all clients using the proxy.. This attack appear to be exploitable v | ||
| CVE-2016-10003 | Hig | 7.5 | < 3.5.21-25.1 | 3.5.21-25.1 | Jan 27, 2017 | Incorrect HTTP Request header comparison in Squid HTTP Proxy 3.5.0.1 through 3.5.22, and 4.0.1 through 4.0.16 results in Collapsed Forwarding feature mistakenly identifying some private responses as being suitable for delivery to multiple clients. | |
| CVE-2016-10002 | Hig | 7.5 | < 3.5.21-25.1 | 3.5.21-25.1 | Jan 27, 2017 | Incorrect processing of responses to If-None-Modified HTTP conditional requests in Squid HTTP Proxy 3.1.10 through 3.1.23, 3.2.0.3 through 3.5.22, and 4.0.1 through 4.0.16 leads to client-specific Cookie data being leaked to other clients. Attack requests can easily be crafted by | |
| CVE-2014-9749 | — | < 3.5.21-25.1 | 3.5.21-25.1 | Nov 6, 2015 | Squid 3.4.4 through 3.4.11 and 3.5.0.1 through 3.5.1, when Digest authentication is used, allow remote authenticated users to retain access by leveraging a stale nonce, aka "Nonce replay vulnerability." |
- CVE-2019-18679Nov 26, 2019affected < 3.5.21-26.20.1fixed 3.5.21-26.20.1
An issue was discovered in Squid 2.x, 3.x, and 4.x through 4.8. Due to incorrect data management, it is vulnerable to information disclosure when processing HTTP Digest Authentication. Nonce tokens contain the raw byte value of a pointer that sits within heap memory allocation. T
- CVE-2019-12529Jul 11, 2019affected < 3.5.21-26.17.1fixed 3.5.21-26.17.1
An issue was discovered in Squid 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7. When Squid is configured to use Basic Authentication, the Proxy-Authorization header is parsed via uudecode. uudecode determines how many bytes will be decoded by iterating over the
- CVE-2019-12525Jul 11, 2019affected < 3.5.21-26.17.1fixed 3.5.21-26.17.1
An issue was discovered in Squid 3.3.9 through 3.5.28 and 4.x through 4.7. When Squid is configured to use Digest authentication, it parses the header Proxy-Authorization. It searches for certain tokens such as domain, uri, and qop. Squid checks if this token's value starts with
- CVE-2019-13345Jul 5, 2019affected < 3.5.21-26.17.1fixed 3.5.21-26.17.1
The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter.
- CVE-2018-1000027Feb 9, 2018affected < 3.5.21-26.6.1fixed 3.5.21-26.6.1
The Squid Software Foundation Squid HTTP Caching Proxy version prior to version 4.0.23 contains a NULL Pointer Dereference vulnerability in HTTP Response X-Forwarded-For header processing that can result in Denial of Service to all clients of the proxy. This attack appear to be e
- CVE-2018-1000024Feb 9, 2018affected < 3.5.21-26.6.1fixed 3.5.21-26.6.1
The Squid Software Foundation Squid HTTP Caching Proxy version 3.0 to 3.5.27, 4.0 to 4.0.22 contains a Incorrect Pointer Handling vulnerability in ESI Response Processing that can result in Denial of Service for all clients using the proxy.. This attack appear to be exploitable v
- affected < 3.5.21-25.1fixed 3.5.21-25.1
Incorrect HTTP Request header comparison in Squid HTTP Proxy 3.5.0.1 through 3.5.22, and 4.0.1 through 4.0.16 results in Collapsed Forwarding feature mistakenly identifying some private responses as being suitable for delivery to multiple clients.
- affected < 3.5.21-25.1fixed 3.5.21-25.1
Incorrect processing of responses to If-None-Modified HTTP conditional requests in Squid HTTP Proxy 3.1.10 through 3.1.23, 3.2.0.3 through 3.5.22, and 4.0.1 through 4.0.16 leads to client-specific Cookie data being leaked to other clients. Attack requests can easily be crafted by
- CVE-2014-9749Nov 6, 2015affected < 3.5.21-25.1fixed 3.5.21-25.1
Squid 3.4.4 through 3.4.11 and 3.5.0.1 through 3.5.1, when Digest authentication is used, allow remote authenticated users to retain access by leveraging a stale nonce, aka "Nonce replay vulnerability."
Page 2 of 2