PatchTheCVEpale moon vulnerabilities and fixes
Recent CVEs affecting pale moon, with upgrade or downgrade steps. 3 tracked.
Also searched as: palemoon.
pale moon has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 3. Most recent: 2020-03-02. Highest priority: CVE-2013-1591 (score 72/100).
- CVE-2020-9545 HIGH 7.5 UPGRADE Pale Moon 28.x before 28.8.4 has a segmentation fault related to module scripting, as demonstrated by a Lacost
- CVE-2018-12292 CRITICAL 9.8 UPGRADE A use-after-free vulnerability exists in DOMProxyHandler::EnsureExpandoObject in Pale Moon before 27.9.3.
- CVE-2013-1591 CRITICAL 9.8 DOWNGRADE MITIGATE Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has un
FAQ
How do I fix pale moon vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is pale moon being exploited right now?
None of the tracked pale moon CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pale moon CVE should I patch first?
CVE-2013-1591 currently ranks highest (72/100): Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has un.