PatchTheCVElibotr vulnerabilities and fixes
Recent CVEs affecting libotr, with upgrade or downgrade steps. 2 tracked.
libotr has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2016-04-07. Highest priority: CVE-2016-2851 (score 74/100).
- CVE-2016-2851 CRITICAL 9.8 MITIGATE MITIGATE Integer overflow in proto.c in libotr before 4.1.1 on 64-bit platforms allows remote attackers to cause a deni
- CVE-2012-3461 MEDIUM 4.3 UPGRADE The (1) otrl_base64_otr_decode function in src/b64.c; (2) otrl_proto_data_read_flags and (3) otrl_proto_accept
FAQ
How do I fix libotr 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 libotr being exploited right now?
None of the tracked libotr CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libotr CVE should I patch first?
CVE-2016-2851 currently ranks highest (74/100): Integer overflow in proto.c in libotr before 4.1.1 on 64-bit platforms allows remote attackers to cause a deni.