PatchTheCVEdeark vulnerabilities and fixes
Recent CVEs affecting deark, with upgrade or downgrade steps. 3 tracked.
deark has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2022-12-19. Highest priority: CVE-2022-43289 (score 41/100).
- CVE-2022-43289 HIGH 7.8 DOWNGRADE Deark v.1.6.2 was discovered to contain a stack overflow via the do_prism_read_palette() function at /modules/
- CVE-2021-28856 MEDIUM 5.5 UPGRADE In Deark before v1.5.8, a specially crafted input file can cause a division by zero in (src/fmtutil.c) because
- CVE-2021-28855 MEDIUM 5.5 UPGRADE In Deark before 1.5.8, a specially crafted input file can cause a NULL pointer dereference in the dbuf_write f
FAQ
How do I fix deark 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 deark being exploited right now?
None of the tracked deark CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which deark CVE should I patch first?
CVE-2022-43289 currently ranks highest (41/100): Deark v.1.6.2 was discovered to contain a stack overflow via the do_prism_read_palette() function at /modules/.