basicsecurity.net
Proof, not just disclosure.
Threats / GNU / CVE-2014-7169
CVE-2014-7169 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

GNU Bourne-Again Shell (Bash) vulnerability

GNU Bash through 4.3 allows remote code execution through environment variable function definitions with trailing strings, enabling arbitrary command execution on affected systems.

Verdict

Today item — known-exploited.

Remote attackers can execute arbitrary code by crafting environment variables containing function definitions with trailing commands. This vulnerability affects systems where Bash processes untrusted environment variables, particularly in CGI scripts, SSH forced commands, and privilege escalation co

CISA KEV Yes · 2022-01-283EPSS 0.9994 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-28).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.9994 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: GNU, Bourne-Again Shell (Bash). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious environment variable containing a Bash function definition with trailing shell commands.
Business
An attacker gains arbitrary code execution on web servers, application servers, or systems accepting remote input through environment variables.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject the payload through CGI parameters, SSH forced commands, or other mechanisms that set environment variables before invoking Bash.
Business
Compromised systems may be used for data theft, lateral movement, or as pivot points for further network compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute commands with the privileges of the Bash process, potentially escalating to higher-privilege contexts.
Business
System integrity is compromised, leading to potential loss of confidentiality, integrity, and availability of critical services and data.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.