squid-cache Squid 2.7 Stable1
Approved changes feed: RSS · Atom
cpe:2.3:a:squid-cache:squid:2.7:stable1:*:*:*:*:*:*part: a version: 2.7 update: stable1
| Vendor | Squid Cache (6232e3cf-8e18-5926-847d-3307ccebc4bf) |
|---|---|
| Product | Squid (9866eca5-f34c-5ae0-9aa7-b68baf8057cd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/squid |
purl2cpe | 2026-06-01 10:14:53.318060 |
pkg:deb/ubuntu/squid |
purl2cpe | 2026-06-01 10:14:53.318062 |
pkg:github/squid-cache/squid |
purl2cpe | 2026-06-01 10:14:53.318063 |
pkg:rpm/fedora/squid |
purl2cpe | 2026-06-01 10:14:53.318065 |
pkg:rpm/opensuse/squid |
purl2cpe | 2026-06-01 10:14:53.318066 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-50269 |
vulnerable | 2026-06-08 06:16:15.868858 |
SQUID-2023:10 Denial of Service in HTTP Request parsing
HIGH (8.6)
Squid is a caching proxy for the Web. Due to an Uncontrolled Recursion bug in versions 2.6 through 2.7.STABLE9, versions 3.1 through 5.9, and versions 6.0.1 through 6.5, Squid may be vulnerable to a Denial of Service attack against HTTP Request parsing. This problem allows a remote client to perform Denial of Service attack by sending a large X-Forwarded-For header when the follow_x_forwarded_for feature is configured. This bug is fixed by Squid version 6.6. In addition, patches addressing this problem for the stable releases can be found in Squid's patch archives.
Published: 2023-12-14T17:09:25.168Z
Updated: 2025-05-21T14:31:00.896Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-12529 |
vulnerable | 2026-06-08 05:12:39.291751 |
Details available
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 input and checking its table. The length is then used to start decoding the string. There are no checks to ensure that the length it calculates isn't greater than the input buffer. This leads to adjacent memory being decoded as well. An attacker would not be able to retrieve the decoded data unless the Squid maintainer had configured the display of usernames on error pages.
Published: 2019-07-11T18:33:55.000Z
Updated: 2024-08-04T23:24:38.470Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.