PatchTheCVEmonostream vulnerabilities
Recent CVEs affecting monostream products. 6 tracked.
monostream has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-08-16. Highest priority: CVE-2022-36155 (score 30/100).
- CVE-2022-36155 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a resource allocation issue via operator new(unsigned long) at asan_new
- CVE-2022-36153 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a segmentation violation via std::vector<unsigned int, std::allocator<u
- CVE-2022-36152 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a memory leak via operator new[](unsigned long) at /asan/asan_new_delet
- CVE-2022-36151 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp.
- CVE-2022-36150 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a heap-buffer overflow via __asan_memmove at /asan/asan_interceptors_me
- CVE-2022-36149 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a heap-use-after-free via temInfoEntry().
FAQ
How do I fix monostream 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 monostream being exploited right now?
None of the tracked monostream CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which monostream CVE should I patch first?
CVE-2022-36155 currently ranks highest (30/100): tifig v0.2.2 was discovered to contain a resource allocation issue via operator new(unsigned long) at asan_new.