Enterprise LinuxOperating system · Redhat
CVE-2023-46846
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQUID is vulnerable to HTTP request smuggling, caused by chunked decoder lenience, allows a remote attacker to perform Request/Response smuggling past firewall and frontend security systems.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQUID is vulnerable to HTTP request smuggling due to chunked decoder lenience, allowing a remote attacker to craft malformed HTTP requests that can bypass firewall and frontend security systems by smuggling requests through the proxy.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 8.0= 9.0
Enterprise Linux EusOperating system
= 8.6= 8.8= 9.0= 9.2
Enterprise Linux For Arm 64Operating system
= 8.0_aarch64
Enterprise Linux For Ibm Z SystemsOperating system
= 8.0_s390x
Enterprise Linux For Power Little EndianOperating system
= 8.0_ppc64le
Enterprise Linux Server AusOperating system
= 8.2= 8.4= 8.6= 9.2
Enterprise Linux Server TusOperating system
= 8.2= 8.4= 8.6= 8.8= 9.2>= 2.6, < 6.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Squid installation and versionRun `squid -v` or `rpm -q squid` to get the installed Squid version numberAffected if Installed version is 2.6 or higher but lower than 6.4, or if the package is from the listed Red Hat Enterprise Linux versions (8.0, 8.2, 8.4, 8.6, 8.8, 9.0, 9.2) that ship with vulnerable Squid versions
-
Verify Squid proxy service is runningRun `systemctl status squid` or check if the proxy is listening on its configured port (default 3128) using `netstat -tlnp | grep squid`Affected if Squid is actively running and accepting connections, making it exposed to network-based request smuggling attacks
-
Inspect chunked encoding handling in configurationReview squid.conf for any non-standard directives related to request parsing. Check logs for rejected chunked requests using `grep -i chunk squid.conf` and review access.log for abnormal patternsAffected if Configuration allows lenient chunked encoding parsing, or logs show inconsistent handling of Transfer-Encoding headers that could indicate smuggling attempts
-
Check for frontline security bypassesReview Squid access logs for requests with duplicate or conflicting Transfer-Encoding and Content-Length headers using `grep -E '(Transfer-Encoding|Content-Length)' /var/log/squid/access.log`Affected if Logs reveal malformed requests with conflicting headers that could have bypassed frontend security systems
Your environment is affected if Squid version is 2.6 through 6.3 (or from the listed RHEL versions) and the proxy is running with default chunked encoding handling, which could allow HTTP request smuggling attacks to bypass security controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.4
Update SQUID to the patched version that fixes the chunked decoder issue and review frontend security configurations to detect request smuggling patterns.
Squid 6.4 or later (specific version depends on RHEL channel - check Red Hat Security Advisory RHSA-2024:0311 or subsequent advisories for exact version)
- Ensure you have a backup of your Squid configuration files (usually in /etc/squid/)
- Update your system package cache: sudo dnf check-update
- Apply the security fix by upgrading the squid package: sudo dnf update squid
- After upgrade, verify the new version is installed: squid -v
- Test your Squid configuration: squid -k parse
- Restart the Squid service to apply changes: sudo systemctl restart squid
- Monitor logs for any issues: sudo journalctl -u squid -f
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46846 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data