Re:Equifax website hacked again, this time to redirect to fa...
by RainaRelanah on Thursday October 12, 2017 @07:09AM
(#15457109)
But there are protections against this, such as HSTS. I would expect someone with as much sensitive information as Equifax to have HSTS + HPKP pinned into the major browsers. Their server should never even receive an HTTP request. It's just unrivaled incompetence.
Re:Equifax website hacked again, this time to redirect to fa...
by discreditable on Thursday October 12, 2017 @07:40AM
(#15457243)
HSTS doesn't help if it's your first visit to the site. To work around that they'd need to get into a preload list.
Re:Equifax website hacked again, this time to redirect to fa...
by andygambles on Thursday October 12, 2017 @07:47AM
(#15457272)
Which is easy if you set preload header.
Re:Equifax website hacked again, this time to redirect to fa...
by tonyztan on Thursday October 12, 2017 @11:33AM
(#15458714)
This. The technology (HSTS, HPKP, Subresource Integrity, upgrade-insecure-requests) is there; sites that need it just don't seem to use it.
Re:Equifax website hacked again, this time to redirect to fa...
by Matt3o12_ on Thursday October 12, 2017 @08:13AM
(#15457381)
Normally, people in marketing don’t write URLs by hand. They copy them and check that they look nice or have a generator make them for them.
So, how did they copy an http url instead of https because they website should have redirected them to https before processing the request (and I just hope that their internal network isn’t compromised).
But don't worry, they'll have an engineer approve it next time as well!