PatchTheCVElibtor vulnerabilities
Recent CVEs affecting libtor products. 6 tracked.
libtor has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-03-01. Highest priority: CVE-2024-27572 (score 50/100).
- CVE-2024-27572 HIGH 7.5 MITIGATE LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the updateCu
- CVE-2024-27571 HIGH 7.5 MITIGATE LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the makeCurR
- CVE-2024-27570 HIGH 7.5 MITIGATE LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the generate
- CVE-2024-27569 MEDIUM 6.5 MITIGATE LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the init_nvr
- CVE-2024-27568 MEDIUM 6.5 MITIGATE LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the apn_name_3g parameter in the setupE
- CVE-2024-27567 MEDIUM 6.5 MITIGATE LBT T300- T390 v2.2.1.8 were discovered to contain a stack overflow via the vpn_client_ip parameter in the con
FAQ
How do I fix libtor 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 libtor being exploited right now?
None of the tracked libtor CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libtor CVE should I patch first?
CVE-2024-27572 currently ranks highest (50/100): LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the updateCu.