SMU versions before 14.8.7825.01 contain an authorization flaw in access to configuration backups. An authenticated user assigned a Storage, Server, or combined Server+Storage administrative role can manipulate a URL to retrieve an SMU configuration backup despite that backup normally being restricted from those roles.
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 (1 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2023-6538, an Insecure Direct Object Reference (IDOR) vulnerability in Hitachi NAS System Management Unit (SMU) versions prior to 14.8.7825.01. The repository contains three files: the main exploit script (CVE-2023-6538.py), a README.md with detailed vulnerability and exploitation information, and a LICENSE file. The Python script requires the attacker to supply the target host, valid JSESSIONID and JSESSIONIDSSO cookies, and a server ID. It then sends an authenticated GET request to a specific SMU endpoint to download a configuration backup archive (registry_data.tgz). This archive may contain sensitive files, including /etc/shadow from the managed server, leading to potential credential compromise. The exploit demonstrates the ability to enumerate and download configuration data for different servers by manipulating the serverid parameter. The attack vector is network-based, requiring access to the SMU's web interface over HTTPS. The exploit is a PoC and does not provide post-exploitation payloads beyond the file download.
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.