dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2023-46847

HIGH · 7.5 CVSS v3.1 Published 2023-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
High EPSS Remotely reachable No privileges Zero-click

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 · unedited
Squid is vulnerable to a Denial of Service, where a remote attacker can perform buffer overflow attack by writing up to 2 MB of arbitrary data to heap memory when Squid is configured to accept HTTP Digest Authentication.

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 confidence

Squid contains a buffer overflow vulnerability in its HTTP Digest Authentication implementation where a remote attacker can write up to 2 MB of arbitrary data to heap memory, causing denial of service.

MitigationDisable HTTP Digest Authentication in Squid configuration if not required, or apply vendor patches when available.

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
Affected:= 8.0= 9.0
Enterprise Linux EusOperating system
Affected:= 8.6= 8.8= 9.0= 9.2
Enterprise Linux For Arm 64Operating system
Affected:= 8.0_aarch64
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 8.0_s390x
Enterprise Linux For Power Little EndianOperating system
Affected:= 8.0_ppc64le
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux Server AusOperating system
Affected:= 8.2= 8.4= 8.6= 9.2
Enterprise Linux Server TusOperating system
Affected:= 8.2= 8.4= 8.6= 8.8= 9.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Squid installation and version
    Run 'squid -v' or 'rpm -q squid' to determine the installed Squid package version
    Affected if The installed version matches one of the Red Hat Enterprise Linux versions listed in the affected products (7.0, 8.0, 8.2, 8.4, 8.6, 8.8, 9.0, 9.2) and the corresponding package is installed
  2. Locate Squid configuration file
    The default Squid configuration is typically located at /etc/squid/squid.conf. Check your system for the actual config file path using 'squid -k parse 2>&1' or review init scripts
    Affected if A Squid configuration file exists and HTTP Digest Authentication is configured
  3. Verify HTTP Digest Authentication is enabled
    Search the Squid configuration file for 'auth_param digest' directives. Also check for any 'acl' entries referencing digest authentication and corresponding 'http_access' rules that use those ACLs
    Affected if The configuration contains 'auth_param digest' lines indicating HTTP Digest Authentication is active, and this authentication method is referenced in access control rules
  4. Check for active authentication proxies
    Review http_access rules to determine if proxy authentication is required. Look for rules that would allow external attackers to reach the Digest Authentication handler
    Affected if Squid is configured to authenticate users via Digest Authentication and the proxy is accessible to remote attackers (not firewalled or limited to trusted networks)

A system is affected if it runs a Squid version matching the listed Red Hat Enterprise Linux versions with HTTP Digest Authentication enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable HTTP Digest Authentication in Squid configuration if not required, or apply vendor patches when available.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46847 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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