Disqus Security Alert: User Info Breach

Re:Disqus Security Alert: User Info Breach by tptacek on Friday October 06, 2017 @09:04PM (#15421631)

Using SHA-1 for password storage would be sev:low in a pentest. There are a lot of other sev:low things that you would certainly agree are signs of incompetence. Unsoundness of engineering and vulnerability impact are almost orthogonal.

[ Parent | on HN ]

Re:Disqus Security Alert: User Info Breach by sillysaurus3 on Saturday October 07, 2017 @11:03AM (#15424021)

The issue is that companies can basically ignore sev:low findings. "Malpractice" implies that they need to care; they do not.

I wish they did. It would be nice if they were forced to care. But it wouldn't block them from being declared secure by a pentest. Low-severity findings are findings, yes, but they don't have the same pull as medium or high severity vulns.

All of this is true for storing passwords in plaintext, too. If some company leaked plaintext passwords, people would be outraged. Yet pentests would still give that company a pass, because plaintext password storage is sev:low.

[ Parent | on HN ]

Re:Disqus Security Alert: User Info Breach by tptacek on Saturday October 07, 2017 @11:33AM (#15424139)

I understand what you're saying, but second-order findings on pentests don't get high severity, no matter how important a sign of unsoundness they are. Severity and importance are also somewhat orthogonal.

[ Parent | on HN ]