We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I tried replicating the attack but my DLL is loaded as the user running cp_client and not as SYSTEM. Any ideas?
The text was updated successfully, but these errors were encountered:
@bananabr Did you ever sort it out? I'm having the same issue.
Sorry, something went wrong.
Obviously, I'd need more information to troubleshoot this. Windows version, driver version, etc.
I have access to some older versions of Windows at home and will test those when I get off work.
Info from the client PC:
This is the driver that was installed when connecting to the malicious printer.
From Get-PrinterDriver:
Get-PrinterDriver
From lmud1040.GDL
lmud1040.GDL
<GDL_ATTRIBUTE Name="*GPDFileVersion" xsi:type="GDLW_string">2.10.0.5</GDL_ATTRIBUTE> <GDL_ATTRIBUTE Name="*GPDSpecVersion" xsi:type="GDLW_string">1.0</GDL_ATTRIBUTE>
Hotfixes: KB5015730 KB5003791 KB5012170 KB5016616 KB5014671 KB5015895 KB5005699
No branches or pull requests
I tried replicating the attack but my DLL is loaded as the user running cp_client and not as SYSTEM. Any ideas?
The text was updated successfully, but these errors were encountered: