CVE-2014-7169 remediation guide

GNU Bourne-Again Shell (Bash)

GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown other impact via a crafted environment, as demonstrated by vectors involving the ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules in the Apache HTTP Server, scripts executed by unspecified DHCP clients, and other situations in which setting the environment occurs across a privilege boundary from Bash execution. NOTE: this vulnerability exists because of an...

Open CVE record

ProductGNU Bourne-Again Shell (Bash)

Affected versions<= 4.3, >= 4.9.0 < 4.9.12, >= 4.10.0 < 4.10.9, >= 4.11.0 < 4.11.11, >= 4.12.0 < 4.12.9, >= 4.13.0 < 4.13.9, >= 4.14.0 < 4.14.4f, 4, 5, 6, < 4.1.1, 4.1.1, 3.0, 4.0, 2.1, 3.4, 5.0, 6.0, 7.0

Fixed versions4.9.12, 4.10.9, 4.11.11, 4.12.9, 4.13.9, 4.14.4f, 4.1.1, 1.2.1, 1.4.3.5, 1.5.0.4, 7.2.0.9, 7.3.0.7, 7.1.0.11, 3.8.0.07, 3.9.1.08, 4.1.2.06, r77.30, 9.3.67.5r1, 10.1.129.11r1, 10.5.52.11r1

Priority basisImmediate · CVSS 9.8 · EPSS 99.9%

Identify the affected asset

Confirm whether GNU Bourne-Again Shell (Bash) 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.

Validate the affected-version match

Compare the deployed version with the affected range: <= 4.3, >= 4.9.0 < 4.9.12, >= 4.10.0 < 4.10.9, >= 4.11.0 < 4.11.11, >= 4.12.0 < 4.12.9, >= 4.13.0 < 4.13.9, >= 4.14.0 < 4.14.4f, 4, 5, 6, < 4.1.1, 4.1.1, 3.0, 4.0, 2.1, 3.4, 5.0, 6.0, 7.0. Treat incomplete inventory results as unresolved.

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.

Apply supported remediation

Apply updates per vendor instructions.

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.