CVE-2021-35616 is an improper authorization vulnerability in the UI Infrastructure component of Oracle Transportation Management 6.4.3. A low-privileged, authenticated attacker with network access to the application over HTTP can exploit the flaw to access data and perform unauthorized data modifications within the scope of accessible Oracle Transportation Management data.
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 Python exploit tool (OracleOTM.py) targeting Oracle Transportation Management (OTM) via CVE-2021-35616. The tool is modular and supports several attack modes: username enumeration, default credential checking, password spraying, arbitrary SQL query execution, and full exploitation via file upload (JSP webshell). The main attack vector is the DBXML servlet endpoint ('/GC3/glog.integration.servlet.DBXMLServlet?command=xmlExport'), which is abused for authentication attempts, SQL injection, and file upload. The exploit can extract sensitive information from the database (OS, DB version, user hashes, file locations) and achieve remote code execution by uploading a JSP file. The repository consists of the main exploit script and a README with usage instructions. The exploit is operational, requiring attacker-supplied host and user lists, and is effective against vulnerable Oracle OTM deployments with the DBXML servlet exposed.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.