PatchTheCVEdjango-anymail vulnerabilities and fixes
Recent CVEs affecting django-anymail, with upgrade or downgrade steps. 2 tracked.
Also searched as: django anymail.
django-anymail has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2018-03-13. Highest priority: CVE-2018-6596 (score 63/100).
- CVE-2018-6596 CRITICAL 9.1 UPGRADE MITIGATE webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the
- CVE-2018-1000089 HIGH 7.4 UPGRADE Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AU
FAQ
How do I fix django-anymail 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 django-anymail being exploited right now?
None of the tracked django-anymail CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which django-anymail CVE should I patch first?
CVE-2018-6596 currently ranks highest (63/100): webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the.