4 ms·

And this boys and girls is why they don't let us run vuln scans on production during work hours (or unplanned). I've worked at at least two companies where a sc

And this boys and girls is why they don't let us run vuln scans on production during work hours (or unplanned). I've worked at at least two companies where a scan caused some important device to crash and have business impact because the scan packets were unusual. They will fire you if you mistakenly ran the scan against a prod asset.

yjftsjthsd-h 7y ago
I understand that it should be structured to minimize risk, but if your prod stack can be taken down by a scan... you really do want to find that out in a controlled manner and not because a script kiddie decided to do the same test.
- wil421 7y ago
  You don’t know what you don’t know. There was a UNIX bug that caused the system to crash or execute code just by being fingered.[1] > Connect to your fingerd daemon and type more than 528 (= 512 + 16) characters (any will do). If your daemon crashes or terminates the connection with no data sent back, you probably have the vulnerability. [1] http://seclab.cs.ucdavis.edu/projects/vulnerabilities/doves/1.html http://seclab.cs.ucdavis.edu/projects/vulnerabilities/doves/...