CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2024-4577 remediation guide

PHP Group PHP

In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, when using Apache and PHP-CGI on Windows, if the system is set up to use certain code pages, Windows may use "Best-Fit" behavior to replace characters in command line given to Win32 API functions. PHP CGI module may misinterpret those characters as PHP options, which may allow a malicious user to pass options to PHP binary being run, and thus reveal the source code of scripts, run arbitrary PHP code on the server, etc.

Open CVE record
ProductPHP Group PHP
Affected versions8.1.*, 8.2.*, 8.3.*, 8.1.0, 8.2.0, 8.3.0, >= 8.1.0 < 8.1.29, >= 8.2.0 < 8.2.20, >= 8.3.0 < 8.3.8, 39, 40
Fixed versions8.1.29, 8.2.20, 8.3.8
Priority basisImmediate · CVSS 9.8 · EPSS 100.0%
01

Identify the affected asset

Confirm whether PHP Group PHP 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: 8.1.*, 8.2.*, 8.3.*, 8.1.0, 8.2.0, 8.3.0, >= 8.1.0 < 8.1.29, >= 8.2.0 < 8.2.20, >= 8.3.0 < 8.3.8, 39, 40. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

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.

CVE-2024-4577 Remediation Guide | SECUFOCUS NOW