libesedb project vulnerabilities
Recent CVEs affecting libesedb project products. 4 tracked.
libesedb project has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2018-09-01. Highest priority: CVE-2018-15161 (score 46/100).
- CVE-2018-15161 MEDIUM 6.5 UPGRADE The libesedb_key_append_data function in libesedb_key.c in libesedb through 2018-04-01 allows remote attackers
- CVE-2018-15160 MEDIUM 6.5 UPGRADE The libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb through 2018-04-01
- CVE-2018-15159 MEDIUM 6.5 UPGRADE The libesedb_page_read_tags function in libesedb_page.c in libesedb through 2018-04-01 allows remote attackers
- CVE-2018-15158 MEDIUM 6.5 UPGRADE The libesedb_page_read_values function in libesedb_page.c in libesedb through 2018-04-01 allows remote attacke
FAQ
How do I fix libesedb 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 libesedb project being exploited right now?
None of the tracked libesedb project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libesedb project CVE should I patch first?
CVE-2018-15161 currently ranks highest (46/100): The libesedb_key_append_data function in libesedb_key.c in libesedb through 2018-04-01 allows remote attackers.