CVE-2014-6271: GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

CVE-2014-6271 · Severity: critical · CVSS 9.8 · Exploited in the wild · Published 2022-01-28

GNU Bash through 4.3 incorrectly processes trailing strings after function definitions in environment variable values. This allows remote attackers to execute arbitrary code when environment variables are set across a privilege boundary, such as in OpenSSH ForceCommand, Apache mod_cgi, or DHCP client scripts.

Vendors: Gnu.

Quick answers

Is CVE-2014-6271 exploited in the wild?
Yes. CVE-2014-6271 is known to be exploited in the wild, first recorded on 28 January 2022. Treat it as urgent.
How severe is CVE-2014-6271?
Critical severity, with a CVSS score of 9.8, published 28 January 2022.
Which products and versions are affected?
GNU Bash through 4.3.
Is there a fix for CVE-2014-6271?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2014-6271 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-2014-6271?
Check whether you run Gnu Bourne-Again Shell (BASH). Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • GNU Bash through 4.3

Timeline

  • 2022-01-28: disclosed: Publication date of the advisory.
  • exploited: Reported as exploited in the wild.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.