A privilege escalation vulnerability exists in trojan versions 2.0.0 through 2.15.3 due to improper access control on the initialization interface /auth/register. A remote attacker can exploit this flaw to escalate privileges by registering through this interface.
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 demonstrates an exploit for an authentication bypass vulnerability in Jrohy/trojan (versions v2.0.0 to v2.15.3). The vulnerability exists because the /auth/register endpoint, intended for initial setup, remains accessible after configuration, allowing unauthenticated users to reset the administrator password. The repository contains two README files (in English and Chinese) explaining the vulnerability and a Python proof-of-concept script (poc.py). The script takes a target URL and a new password as arguments, hashes the password, and sends a POST request to the /auth/register endpoint to set the new admin password. The exploit is a proof-of-concept and does not provide post-exploitation capabilities beyond password reset. The main attack vector is network-based, targeting the exposed HTTP endpoint. No hardcoded IPs or domains are present; the script requires the user to supply the target URL.
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.