A directory traversal vulnerability exists in Payara Micro Community versions 5.2021.6 and below. The flaw allows attackers to manipulate file paths in such a way that they can access files and directories outside the intended web root or application directory, potentially exposing sensitive files on the server.
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 (1 hidden).
This repository provides a proof-of-concept (POC) exploit for CVE-2021-41381, a directory traversal vulnerability in Payara Micro Community version 5.2021.6. The repository contains two files: a markdown README and a main exploit description file ('CVE: 2021-41381-POC'). The exploit demonstrates how an attacker can use a crafted HTTP request (with the --path-as-is curl option) to access sensitive configuration files on the server, specifically '/.//WEB-INF/classes/META-INF/microprofile-config.properties'. The exploit is executed by appending the traversal path to the base URL of a vulnerable Payara Micro instance and checking the response for specific configuration strings. The POC is operational for both Linux and Windows deployments of the target software. No weaponized or automated script is provided; the exploit is manual and intended for demonstration and verification purposes.
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.
1 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.