PatchTheCVEapersistence vulnerabilities and fixes
Recent CVEs affecting apersistence, with upgrade or downgrade steps. 1 tracked.
apersistence has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2023-01-17. Highest priority: CVE-2017-20171 (score 33/100).
- CVE-2017-20171 MEDIUM 5.5 UPGRADE A vulnerability classified as critical has been found in PrivateSky apersistence
FAQ
How do I fix apersistence 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 apersistence being exploited right now?
None of the tracked apersistence CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which apersistence CVE should I patch first?
CVE-2017-20171 currently ranks highest (33/100): A vulnerability classified as critical has been found in PrivateSky apersistence.