Splunk removed a hunting analytic after the underlying vulnerabilities were patched in current releases, but the detection documented how low-privilege users could attempt to access hashed Splunk passwords through the conf-user-seed REST endpoint. The analytic monitored splunkd_web access logs for requests to that endpoint because such activity could expose credential material and support privilege escalation to full administrative control of a Splunk instance.
The activity was mapped to MITRE ATT&CK technique T1212 (Exploitation for Credential Access), which covers abuse of software flaws to obtain credentials or bypass authentication controls. MITRE notes that this class of exploitation can enable forged authentication artifacts, replayed authentication traffic, unintended token creation or renewal in cloud environments, and broader privilege escalation when credentialing systems are affected.

Get the actors, campaigns, and ATT&CK mapping behind it.
2 events from the most recent confirmed update back to the earliest known activity.
Splunk Threat Research removed the detection "Splunk Low Privilege User Can View Hashed Splunk Password" from its content library, stating that the associated CVEs had been patched in the latest Splunk release. The removal was noted in content library version 5.6.0.
MITRE ATT&CK published technique T1212, "Exploitation for Credential Access," describing how adversaries exploit software vulnerabilities to obtain credentials or bypass authentication, including examples such as MS14-068 and replay attacks.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.