3 ms·

Fixed many months ago just being made public now, according to the bug tracker. Why a 7 month delay?

• gpvos 2y ago
  Citation needed.
• Brybry 2y ago
  I didn't get the ESR 128.3.1 update until yesterday.
• pixelesque 2y ago
  Why the need for patch releases then like 128.3.1?
  • suprjami 2y ago
    128 is the current ESR: https://whattrainisitnow.com/calendar/ https://whattrainisitnow.com/calendar/
• hannob 2y ago
  What are you talking about? The fix was released today, and FF says they received the report 25 hours before that: https://infosec.exchange/@attackanddefense/113282079430280742 https://infosec.exchange/@attackanddefense/11328207943028074...
• okasaki 2y ago
  "Fixed in Firefox 131.0.2" which was released 21 hours ago? (https://ftp.mozilla.org/pub/firefox/releases/131.0.2/ https://ftp.mozilla.org/pub/firefox/releases/131.0.2/)
• jokoon 2y ago
  Because if you make it public too early, it gives some time for attackers to write exploit to target unpatched versions. Firefox is used in other projects, so the patch needs to spread, and time is needed.