Loading vulnerability…
CRIXP OpenCRX versions 4.30 and 5.0-20200717 and prior contain a vulnerability where the password change functionality does not properly verify the identity of the requesting user. This allows an attacker with network access to the OpenCRX instance to arbitrarily change the password of any user, including privileged accounts such as admin-Standard, without authentication.
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 provides a proof-of-concept exploit for CVE-2020-7378, targeting OpenCRX versions up to and including 5.0-20200717. The exploit chains two vulnerabilities: (1) predictable password reset tokens due to insecure use of java.util.Random, and (2) a blind XXE vulnerability in the REST API. The repository contains three files: a Java class (OpenCRXToken.java) that emulates the token generation logic for brute-forcing password reset tokens, a Python script (opencrx-reset-spray.py) that automates the attack by requesting a password reset, generating tokens, and attempting to reset the password, and a README.md with detailed usage instructions and vulnerability background. The Python script also crafts and sends a malicious XML payload to the REST API endpoint to exploit the XXE and exfiltrate sensitive files from the server. The attack is fully unauthenticated and leverages network-accessible endpoints, requiring the attacker to be able to host a DTD file for the XXE. The exploit demonstrates the ability to gain administrative access and read arbitrary files from the server, representing a critical risk to affected OpenCRX installations.
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.