3 ms·

> Wow - only Google seemed to really prioritize fixing this / had the processes and manpower to get a fix out quickly. I would have guessed they'd be the quick

• jbverschoor 2y ago
  Perhaps they had the info before it was disclosed to the others?
  • crtasm 2y ago
    https://www.mozilla.org/en-US/security/advisories/mfsa2025-14/#CVE-2024-9956 https://www.mozilla.org/en-US/security/advisories/mfsa2025-1... links the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1922357 https://bugzilla.mozilla.org/show_bug.cgi?id=1922357 but it's not public, perhaps someone can tell us when it was opened.
    • jbverschoor 2y ago
      The next issue, https://bugzilla.mozilla.org/show_bug.cgi?id=1922358 https://bugzilla.mozilla.org/show_bug.cgi?id=1922358 is from October 2nd 2024
• gavinsyancey 2y ago
  Reading through the Chromium bug report, it looks like the reporter wasn't able to get in contact with Mozilla until February, so after they were aware it only took a month to fix the bug in Firefox. It's unclear when they started trying, and who's fault the delay is.
• mastersplinter 2y ago
  I can't speak to the prioritization differences between the different browser teams, Chrome was definitely the best which isn't surprising considering their resources. Apple was also quite swift but I imagine it took them some time to decide where to deliver the fix, I myself wasn't sure if this is something that should be blocked at the OS level (the Authentication checking the intent origin) or browser. Mozilla is usually the slowest out of the three but they were still very professional.