CVE REMEDIATION GUIDE
Priority reviewHighFixed-version data available

CVE-2023-46847 remediation guide

Red Hat Red Hat Enterprise Linux 6 Extended Lifecycle Support, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 7.6 Advanced Update Support

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.

Open CVE record
ProductRed Hat Red Hat Enterprise Linux 6 Extended Lifecycle Support, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 7.6 Advanced Update Support
Affected versions>= 3.2.0.1 < 6.4, 8.0, 9.0, 8.6, 8.8, 9.2, 8.0 aarch64, 8.0 s390x, 8.0 ppc64le, 7.0, 8.2, 8.4
Fixed versions6.4
Priority basisPriority · CVSS 7.5 · EPSS 88.4%
01

Identify the affected asset

Confirm whether Red Hat Red Hat Enterprise Linux 6 Extended Lifecycle Support, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 7.6 Advanced Update Support is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 3.2.0.1 < 6.4, 8.0, 9.0, 8.6, 8.8, 9.2, 8.0 aarch64, 8.0 s390x, 8.0 ppc64le, 7.0, 8.2, 8.4. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.4. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.