Enterprise LinuxOperating system · Redhat
CVE-2023-46848
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 Denial of Service, where a remote attacker can perform DoS by sending ftp:// URLs in HTTP Request messages or constructing ftp:// URLs from FTP Native input.
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 · moderate confidenceSquid proxy server contains a denial of service vulnerability where remote attackers can send specially crafted ftp:// URLs embedded in HTTP request messages or construct ftp:// URLs from FTP Native input, causing the service to become unavailable.
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
= 9.0
Enterprise Linux EusOperating system
= 9.2
Enterprise Linux Server AusOperating system
= 9.2
Enterprise Linux Server TusOperating system
= 9.2>= 5.0.3, < 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify Squid installation and versionRun 'squid -v' or 'rpm -q squid' to get the installed version numberAffected if Version is 5.0.3 or higher but lower than 6.4
-
Confirm the vulnerable FTP URL handling is activeCheck if Squid is configured to process FTP requests - review squid.conf for ftp* directives or verify FTP proxy access is allowedAffected if FTP URL processing or FTP Native input handling is enabled in Squid configuration
-
Verify Squid service is runningRun 'systemctl status squid' or 'ps aux | grep squid' to confirm the service is activeAffected if Squid is running and accepting requests
-
Check for recent indicators of DoSReview Squid access logs and system logs for crashes, timeouts, or excessive resource usage related to FTP URL requestsAffected if Logs show service degradation or crashes when processing FTP URLs
A system is affected if it runs Squid version 5.0.3 or higher but below version 6.4, has FTP URL processing enabled, and the Squid service is active.
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
Upgrade Squid to the latest version or apply the vendor-supplied patch. If immediate patching is not possible, consider restricting or filtering FTP URL processing at the proxy boundary.
Squid 6.4 or later (via Red Hat Enterprise Linux update channels)
- 1. Update the system package cache: sudo dnf check-update
- 2. Upgrade Squid to the fixed version: sudo dnf update squid
- 3. Verify the installed version matches the fixed release (6.4 or later): squid -v
- 4. Restart the Squid service to apply the update: sudo systemctl restart squid
- 5. Verify the service is running correctly: sudo systemctl status squid
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46848 — 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-46848 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