PatchTheCVEliblnk project vulnerabilities
Recent CVEs affecting liblnk project products. 5 tracked.
liblnk project has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2019-10-09. Highest priority: CVE-2018-12098 (score 31/100).
- CVE-2019-17401 LOW 3.3 DOWNGRADE libyal liblnk 20191006 has a heap-based buffer over-read in the network_share_name_offset>20 code block of lib
- CVE-2019-17264 LOW 3.3 UPGRADE In libyal liblnk before 20191006, liblnk_location_information_read_data in liblnk_location_information.c has a
- CVE-2018-12098 MEDIUM 5.5 UPGRADE The liblnk_data_block_read function in liblnk_data_block.c in liblnk through 2018-04-19 allows remote attacker
- CVE-2018-12097 MEDIUM 5.5 UPGRADE The liblnk_location_information_read_data function in liblnk_location_information.c in liblnk through 2018-04-
- CVE-2018-12096 MEDIUM 5.5 UPGRADE The liblnk_data_string_get_utf8_string_size function in liblnk_data_string.c in liblnk through 2018-04-19 allo
FAQ
How do I fix liblnk project 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 liblnk project being exploited right now?
None of the tracked liblnk project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which liblnk project CVE should I patch first?
CVE-2018-12098 currently ranks highest (31/100): The liblnk_data_block_read function in liblnk_data_block.c in liblnk through 2018-04-19 allows remote attacker.