News for hackers. Stuff that matters.
Re:Remote code execution vulnerability in apt/apt-get by ChrisCinelli on Tuesday January 22, 2019 @02:22PM (#18971444)
Incidentally binaries from support.apple.com are also served on http.
Re:Remote code execution vulnerability in apt/apt-get by aboutruby on Tuesday January 22, 2019 @03:40PM (#18972222)
The downloads are in an HTTPS page leading to HTTPS download links, and HTTP redirects to HTTPS: https://support.apple.com/downloads/quicktime for instance.
Re:Remote code execution vulnerability in apt/apt-get by ptx on Wednesday January 23, 2019 @07:54AM (#18977730)
> and HTTP redirects to HTTPS

...or to anywhere a MITM attacker wants to redirect you.

Re:Remote code execution vulnerability in apt/apt-get by ptx on Wednesday January 23, 2019 @04:27PM (#18983163)
I guess some people disagree?

But if any response in the redirect chain is served over HTTP, it can be replaced with a different response containing any "Location" header of the attacker's choosing instead of the original one. So it doesn't matter if the eventual intended URL is an HTTPS URL, because it will never be reached. The redirect will go to the attacker's site instead. (And in the case of a download, the user will never notice because the file URL is usually not prominently displayed.)

So a HTTP response anywhere in a redirect chain is equivalent to serving it over HTTP. Perhaps this was exactly the point of the parent post, but I thought it would be useful to make it explicit.