A directory traversal vulnerability exists in the Issue Collector plugin in Atlassian JIRA prior to version 6.0.4. The vulnerability allows remote attackers to create arbitrary files on the server by exploiting unspecified vectors, likely involving crafted input that traverses directories outside the intended path.
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 (jira_collector_traversal.rb) that exploits a directory traversal vulnerability (CVE-2014-2314) in Atlassian JIRA 6.0.3's Issues Collector feature on Windows. The exploit abuses the file upload mechanism to traverse directories and place a malicious JSP dropper in the JIRA web directory. This dropper writes and executes a custom EXE payload, achieving remote code execution. The module is operational, requiring the attacker to specify the JIRA path, collector ID, and traversal depth. The main attack vector is network-based, targeting the JIRA web interface (default port 8080). The code is structured as a typical Metasploit exploit, with functions for checking the target, generating payloads, uploading files via traversal, and executing the payload. The endpoints involved include the JIRA REST API for attachments and the login page for version detection. The exploit is not a detection script or a fake; it is a real, working exploit module for Metasploit.
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.