Loading vulnerability…
CVE-2011-4350 is a directory traversal vulnerability in Yaws 1.91, a web server written in Erlang. The vulnerability allows a remote, authenticated user to access arbitrary files on the server by sending specially crafted URL requests that traverse directories outside the intended web root. The flaw is similar to CVE-2010-4181 and can be exploited to read sensitive files such as /etc/passwd, provided the Yaws process has sufficient permissions.
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 auxiliary module (modules/auxiliary/scanner/http/yaws_traversal.rb) that exploits a directory traversal vulnerability in Yaws Web Server version 1.9.1 or less (CVE-2011-4350). The module allows an attacker to retrieve arbitrary files from the server's filesystem by sending a specially crafted HTTP GET request with directory traversal sequences in the URI. The module is configurable for the target port (default 8080) and the file path to retrieve (default is 'windows\win.ini'). The exploit does not provide code execution but can be used to read sensitive files. The code is written in Ruby and is designed to be run within the Metasploit framework. No hardcoded IPs or domains are present; the endpoint is constructed dynamically based on user input. The module is a proof-of-concept for file read via directory traversal.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.