CVE-2022-29917

Reference Links

• https://bugzilla.mozilla.org/buglist.cgi?bug_id=1684739%2C1706441%2C1753298%2C1762614%2C1762620%2C1764778
• https://www.mozilla.org/en-US/security/advisories/mfsa2022-17/
• https://www.mozilla.org/en-US/security/advisories/mfsa2022-16/
• https://bugzilla.mozilla.org/buglist.cgi?bug_id=1684739%2C1706441%2C1753298%2C1762614%2C1762620
• https://www.mozilla.org/en-US/security/advisories/mfsa2022-18/
• https://www.mozilla.org/security/advisories/mfsa2022-16/
• https://www.mozilla.org/security/advisories/mfsa2022-17/
• https://www.mozilla.org/security/advisories/mfsa2022-18/

Parent vulnerabilities

(Appears in the following advisories)

• MFSA2022-18
• MFSA2022-16
• MFSA2022-17

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-1520
• CVE-2022-29914
• CVE-2022-29909
• CVE-2022-29916
• CVE-2022-29911
• CVE-2022-29912
• CVE-2022-29913
• CVE-2022-29917
• CVE-2022-29910
• CVE-2022-29915
• CVE-2022-29918

Frequently Asked Questions

• What is the severity of CVE-2022-29917?

  CVE-2022-29917 is categorized as a memory safety vulnerability which can potentially lead to memory corruption.

• How do I fix CVE-2022-29917?

  To fix CVE-2022-29917, update to Firefox versions 100 or later, or Firefox ESR version 91.9.

• Which versions of software are affected by CVE-2022-29917?

  CVE-2022-29917 affects Firefox versions up to 99, Firefox ESR versions up to 91.8, and Thunderbird versions up to 91.8.

• Can CVE-2022-29917 be exploited?

  Although it's presumed that with enough effort CVE-2022-29917 could be exploited, there is currently no public evidence of widespread exploitation.

• Who reported CVE-2022-29917?

  CVE-2022-29917 was reported by Mozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter, and the Mozilla Fuzzing Team.