← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2014-6271 exploited? Yes: in CISA KEV since 28 Jan 2022

Gociux · GNU Bourne-Again Shell (Bash) · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2014-6271, GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 28 Jan 2022, 2683 days after it was published. It affects GNU Bourne-Again Shell (Bash). If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 28 Jan 2022
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.8CVSS 3.1 · critical
US federal due28 Jul 2022BOD 22-01 deadline

What it is

GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.

VendorGNU (5 exploited CVEs in KEV)
ProductBourne-Again Shell (Bash)
VulnerabilityGNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
WeaknessCWE-78
Published24 Sep 2014
Added to KEV28 Jan 2022
Reported by (CNA)debian

What to do

  1. Check whether you run it. Look for Bourne-Again Shell (Bash) in your asset inventory, including appliances and cloud images. Stack check lists every exploited GNU CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 24 Sep 2014.
  4. Get told next time. Email alerts when CISA adds a CVE for GNU.

Other exploited CVEs in Bourne-Again Shell (Bash)

References

Questions

Is CVE-2014-6271 being exploited?

Yes. CISA added CVE-2014-6271 to the Known Exploited Vulnerabilities catalog on 28 Jan 2022, which means there is reliable evidence of exploitation in the wild.

Is CVE-2014-6271 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2014-6271?

Apply updates per vendor instructions. Check GNU's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Bourne-Again Shell (Bash) and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in January 2022 · GNU scorecard · act-now radar.

Running GNU in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →