VULNERABILITY:
Firefox only stores up to 1024 HSTS entries.
When the limit is reached, Firefox discards entries based on their age and recent visits to the domain in question.
IMPACT:
The HSTS header ensures that once a page has been visited, the browser will attempt to connect to it using HTTPS. The limit means that Firefox effectively does not store any further HSTS headers, as new ones permanently override each other. Sites without HSTS protection are vulnerable to machine-in-the-middle attacks, especially downgrade attacks such as SSL Stripping.
@willc did you watch the video??
Breaking Out HSTS (and HPKP) On Firefox, IE/Edge and (Possibly) Chrome(from 2017)
https://counter.social/@ecksmc/110972141522056985
and this
(PDF URL)
@ecksmc Not yet, thanks for the links