Loading vulnerability…
GNU Bash through 4.3 bash43-025 incorrectly processes trailing strings following certain malformed function definitions in environment variable values. This issue is an incomplete fix for CVE-2014-6271. When Bash is invoked in a context where an attacker can influence environment variables across a privilege boundary, the malformed definition can cause Bash to process unintended trailing content, enabling command execution and file write behavior. Documented attack surfaces include OpenSSH sshd configurations using ForceCommand, Apache HTTP Server mod_cgi and mod_cgid, DHCP client script execution, and similar situations where untrusted input is translated into environment variables before Bash execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (14 hidden).
This repository is a minimal Shellshock proof-of-concept for CVE-2014-6271. It contains only two files: a Dockerfile that builds a vulnerable GNU Bash 4.3 environment on Ubuntu 14.04, and a README explaining the bug, reproduction steps, and real-world attack surface. The Dockerfile downloads bash-4.3 from ftp.gnu.org, compiles it from source, installs it to /usr/local/bin/bash, and launches that binary in the container. The exploit capability is straightforward command execution during bash initialization by supplying a crafted environment variable containing a function definition followed by trailing shell commands. The README demonstrates this with `env x='() { :;}; echo VULNERABLE' bash -c "echo test"`, which causes the injected `echo VULNERABLE` to run before the intended command. The repository does not include a remote exploit script or automation against a network service; instead it is a local reproduction environment and educational PoC. However, it explicitly documents the real-world web attack vector: CGI applications that pass attacker-controlled HTTP headers such as User-Agent into environment variables before invoking bash. Overall, this is a valid, non-framework PoC repository intended to reproduce and explain Shellshock rather than provide a weaponized exploitation tool.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
44 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A related Bash vulnerability mentioned as a newly identified bug for which proven patches were not yet available at the time of writing.
A specific vulnerability cited as an example of exploiting Internet-facing systems for initial access; no further technical or operational detail is given in the content.
A specific vulnerability cited as an example of exploiting Internet-facing systems for initial access; no further technical detail is given in the content.
A specific vulnerability cited as an example of exploitation of Internet-facing systems; no further technical detail is provided in the content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.