Printnightmare

Description

Automated generation of attack data by exploiting CVE-2021-1675

MITRE ATT&CK Techniques

ID Technique Tactic
T1547.012 Print Processors Persistence, Privilege Escalation

Environment Details

Field Value
Environment attack_range
Directory printnightmare
Test Date 2021-07-01

Datasets

The following datasets were collected during this attack simulation:

Mimikatz-Windows-Sysmon

  • Path: /datasets/attack_techniques/T1547.012/printnightmare/mimikatz-windows-sysmon.log
  • Sourcetype: XmlWinEventLog
  • Source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational

Windows-Sysmon

  • Path: /datasets/attack_techniques/T1547.012/printnightmare/windows-sysmon.log
  • Sourcetype: XmlWinEventLog
  • Source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational

The following detections in our security content repository use this attack data for testing:

Detection Name Type Source MITRE ATT&CK Analytic Story
Spoolsv Writing a DLL - Sysmon TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Black Basta Ransomware
Spoolsv Suspicious Process Access TTP Endpoint T1068 PrintNightmare CVE-2021-34527, Black Basta Ransomware
Spoolsv Writing a DLL TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Compromised Windows Host, Black Basta Ransomware
Spoolsv Suspicious Loaded Modules TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Black Basta Ransomware
Spoolsv Spawning Rundll32 TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Compromised Windows Host, Black Basta Ransomware
Print Spooler Adding A Printer Driver TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Black Basta Ransomware
Print Spooler Failed to Load a Plug-in TTP Endpoint T1547.012 PrintNightmare CVE-2021-34527, Black Basta Ransomware

Usage Instructions

Replay with Splunk Attack Data

Replay attack data with replay.py from Splunk Attack Data.

1python replay.py --dataset /datasets/attack_techniques/T1547.012/printnightmare/mimikatz-windows-sysmon.log --index attack_data

Manual Import

  1. Download the dataset files from the paths listed above
  2. Configure your Splunk instance with the appropriate sourcetypes
  3. Import the logs using the Splunk Add Data wizard

Find more detections and analytics for this attack technique in our security content repository.


Source: GitHub | Version: 1.0