lhasa vulnerabilities and fixes

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

lhasa has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-04-21. Highest priority: CVE-2016-2347 (score 59/100).

• CVE-2016-2347 HIGH 7.8 MITIGATE MITIGATE Integer underflow in the decode_level3_header function in lib/lha_file_header.c in Lhasa before 0.3.1 allows r

FAQ

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

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

Which lhasa CVE should I patch first?

CVE-2016-2347 currently ranks highest (59/100): Integer underflow in the decode_level3_header function in lib/lha_file_header.c in Lhasa before 0.3.1 allows r.

← Back to latest CVEs