Loading vulnerability…
A privilege escalation vulnerability exists in Canonical Juju's 'juju-run' utility prior to versions 1.25.12, 2.0.4, and 2.1.3. The vulnerability arises from the use of a UNIX domain socket with overly permissive permissions, allowing any local user on a Juju-deployed unit to interact with the socket. Since 'juju-run' executes commands as root within a hook context, this flaw enables non-root, non-sudo users with access to the system to execute arbitrary commands as root, thereby escalating their privileges.
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 (modules/exploits/linux/local/juju_run_agent_priv_esc.rb) that exploits a local privilege escalation vulnerability in the Juju agent on Linux systems (CVE-2017-9232). The exploit targets Juju agent versions prior to 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3, which expose a UNIX domain socket with improper permissions, allowing unprivileged users to execute commands as root. The module enumerates available Juju units, checks for privileged sockets, uploads a custom payload (such as a shell or meterpreter executable) to a writable directory (default: /tmp), and executes it as root via the vulnerable agent. The exploit is operational and provides root access if successful. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.