Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

s3ql vulnerabilities and fixes

Recent CVEs affecting s3ql, with upgrade or downgrade steps. 1 tracked.

s3ql has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-06-10. Highest priority: CVE-2018-12088 (score 56/100).

FAQ

How do I fix s3ql 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 s3ql being exploited right now?

None of the tracked s3ql CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which s3ql CVE should I patch first?

CVE-2018-12088 currently ranks highest (56/100): S3QL before 2.27 mishandles checksumming, and consequently allows replay attacks in which an attacker who cont.

← Back to latest CVEs