Issue:
ACAS \ Nessus Causes Systems to Crash, Reboot, or BSOD upon Credentialed Scans
Environment:
Windows 7 workstations
Symptoms:
The moment an ACAS \ Nessus Credentialed scan begins, the target system crashes, reboots, or BSODs.
Solution:
Tracked this down to Microsoft Patch 3161531.
Appears to be happening when Tenable accesses C$ (almost immediately upon scan).
A related discussion on BSOD's when accessing C$ is here:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/4b1e0e7b-3b26-41f3-8979-0cd7a25d9209/kb3161561-crashing-server-when-remotly-accessed-with-smb?forum=winservergen
It appears that Microsoft has put out a related hotfix to this issue. Not because of Nessus specifically, but due to general problems when accessing C$, which I believe is ultimately why Nessus is failing.
For details, see both:
https://support.microsoft.com/en-us/kb/3161561
https://support.microsoft.com/en-us/kb/3179573
ACAS \ Nessus Causes Systems to Crash, Reboot, or BSOD upon Credentialed Scans
Environment:
Windows 7 workstations
Symptoms:
The moment an ACAS \ Nessus Credentialed scan begins, the target system crashes, reboots, or BSODs.
Solution:
Tracked this down to Microsoft Patch 3161531.
Appears to be happening when Tenable accesses C$ (almost immediately upon scan).
A related discussion on BSOD's when accessing C$ is here:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/4b1e0e7b-3b26-41f3-8979-0cd7a25d9209/kb3161561-crashing-server-when-remotly-accessed-with-smb?forum=winservergen
It appears that Microsoft has put out a related hotfix to this issue. Not because of Nessus specifically, but due to general problems when accessing C$, which I believe is ultimately why Nessus is failing.
For details, see both:
https://support.microsoft.com/en-us/kb/3161561
https://support.microsoft.com/en-us/kb/3179573
No comments:
Post a Comment