kavita vulnerabilities and fixes
Recent CVEs affecting kavita, with upgrade or downgrade steps. 4 tracked.
kavita has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2023-02-19. Highest priority: CVE-2022-3993 (score 60/100).
- CVE-2023-0919 HIGH 8.1 UPGRADE Missing Authentication for Critical Function in GitHub repository kareadita/kavita prior to 0.7.0.
- CVE-2022-3993 CRITICAL 9.4 UPGRADE Improper Restriction of Excessive Authentication Attempts in GitHub repository kareadita/kavita prior to 0.6.0
- CVE-2022-3945 MEDIUM 5.3 UPGRADE Improper Restriction of Excessive Authentication Attempts in GitHub repository kareadita/kavita prior to 0.6.0
- CVE-2022-2756 MEDIUM 6.5 UPGRADE Server-Side Request Forgery (SSRF) in GitHub repository kareadita/kavita prior to 0.5.4.1.
FAQ
How do I fix kavita 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 kavita being exploited right now?
None of the tracked kavita CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which kavita CVE should I patch first?
CVE-2022-3993 currently ranks highest (60/100): Improper Restriction of Excessive Authentication Attempts in GitHub repository kareadita/kavita prior to 0.6.0.