cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

Thank you as always Daveb3d...Your comments are always well received.

Much appreciated.

 

 

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

The spoolersv shouldn't have child processes running. Is there a way to write an expert rule, which blocks spoolersv from creating a child process?

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

Oddly, it can...  but this rule would block that (and I put in a spot for FPs)

Rule {
	Process {
		Include OBJECT_NAME { -v "spoolsv.exe" }

	}
	Target {
		Match PROCESS {
			Include OBJECT_NAME { -v "**" }
			#Exclude OBJECT_NAME { -v "whatever.exe" }
			Include -access "CREATE"
		}
	}
}

 

This rule is more targeted but also covers more threats with it.

Rule {
	Process {
		Include OBJECT_NAME { -v "spoolsv.exe" }
	}
	Target {
	#block spawning of OS processes for injection purposes (e.g. CobaltStrike Spawn_to) or other uses (recon, cmd, powershell)
		Match PROCESS {
			Include OBJECT_NAME { -v "c:\\windows\\**" }
			Include -access "CREATE"
		}

		#block injection into running OS processes for process migration (e.g. Meterpreter migrate)
		Match PROCESS {
				Include OBJECT_NAME { -v "c:\\windows\\**" }
				Include -nt_access "!0x0020"
		}
		#block cred theft from lsass
		Match PROCESS {
			Include OBJECT_NAME { 
				-v "lsass.exe"
			}
			Include -nt_access "!0x0010"
		}
	}
}
TravisNC
Level 7
Report Inappropriate Content
Message 34 of 50

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution
Following, because this is about to be a trainwreck and hopefully McAfee has some rules available soon.

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

See my post at https://community.mcafee.com/t5/Endpoint-Security-ENS/ENS-10-7-Servers-CVE-2021-1675-Print-Spooler-0...

Rule {
	Process {
		Include OBJECT_NAME { -v "spoolsv.exe" }
	}
	Target {
		Match FILE {
			Include OBJECT_NAME { -v "C:\\Windows\\System32\\spool\\drivers\\x64\\3\\kernelbase.dll" }
			Include -access "CREATE"
		}
	}
}
Pravas
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 36 of 50

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

Hi All,

The vulnerability is still under investigation. Meanwhile McAfee recommends to disable Print Spooler Service on all Servers.

https://kc.mcafee.com/corporate/index?page=content&id=KB94659

Thanks

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

SharpPrintNightmare defeats my rule above..  updated to include coverage there:

 

Rule {
	Process {
		Include OBJECT_NAME { -v "spoolsv.exe" }
	}
	Target {
		Match FILE {
			Include OBJECT_NAME { 
            -v "C:\\Windows\\System32\\spool\\drivers\\x64\\3\\kernelbase.dll"
            -v "C:\\Windows\\System32\\spool\\drivers\\x64\\3\\winhttp.dll"
            }
			Include -access "CREATE"
		}
	}
}

 

 

Korny
Level 9
Report Inappropriate Content
Message 38 of 50

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution
You solution doesn't work for me, so I changed it to this:
Rule {

Process {
Include OBJECT_NAME { -v "spoolsv.exe" }
}
Target {
Match FILE {
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\kernelbase.dll" }
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\winhttp.dll" }


Include -access "CREATE"
}
}
}
ChrisQ
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 39 of 50

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

I don't have much experience with custom rules. 

Can anyone confirm the following two rules are pretty much the same and the Match FILE section can be written in either way? 

Rule {
Process {
Include OBJECT_NAME { -v "spoolsv.exe" }
}
Target {
Match FILE {
Include OBJECT_NAME {
-v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\kernelbase.dll"
-v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\winhttp.dll"
-v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\ntdll.dll"
-v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\kernel32.dll"
-v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\user32.dll"
}
Include -access "CREATE"
}
}
}

 

Rule {

Process {
Include OBJECT_NAME { -v "spoolsv.exe" }
}
Target {
Match FILE {
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\kernelbase.dll" }
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\winhttp.dll" }
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\ntdll.dll" }
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\kernel32.dll" }
Include OBJECT_NAME { -v "%systemroot%\\System32\\spool\\drivers\\x64\\3\\user32.dll" }


Include -access "CREATE"
}
}
}

 

 

Re: McAfee coverage on - CVE-2021-1675 (PrintNightmare 0-day exploit)

Jump to solution

Yup..  both will work.  I do basically all my rules the first way.  

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community