Loading vulnerability…
CVE-2017-16894 affects Laravel Framework through 5.5.21. The issue is in Laravel's writeNewEnvironmentFileWith function in src/Illuminate/Foundation/Console/KeyGenerateCommand.php, which uses file_put_contents to write the .env file without restricting its filesystem permissions. As a result, remote attackers can obtain sensitive information by directly requesting the /.env URI when the file is exposed by the web server. Disclosed data may include secrets stored in the environment file, such as externally usable passwords and other application configuration values.
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.
This repository contains a single Metasploit module: 'laravel_token_unserialize_exec.rb', which exploits a remote command execution vulnerability in the PHP Laravel Framework (CVE-2018-15133, CVE-2017-16894). The exploit targets Laravel versions 5.5.40 and 5.6.x up to 5.6.29, leveraging insecure unserialize operations in the handling of the X-XSRF-TOKEN HTTP header. The module can also check for APP_KEY leakage via the /.env file or error messages. Successful exploitation allows an attacker to execute arbitrary system commands on the target server, typically resulting in a reverse shell. The module is weaponized, supporting customizable payloads via the Metasploit framework. The only file present is the exploit module itself, written in Ruby, and it is fully integrated with Metasploit's payload and session management.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.