tifig
by monostream
CVEs (6)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-36155 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a resource allocation issue via operator new(unsigned long) at asan_new_delete.cpp. | ||
| CVE-2022-36153 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a segmentation violation via std::vector<unsigned int, std::allocator >::size() const at /bits/stl_vector.h. | ||
| CVE-2022-36152 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a memory leak via operator new[](unsigned long) at /asan/asan_new_delete.cpp. | ||
| CVE-2022-36151 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp. | ||
| CVE-2022-36150 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a heap-buffer overflow via __asan_memmove at /asan/asan_interceptors_memintrinsics.cpp. | ||
| CVE-2022-36149 | Med | 0.36 | 5.5 | 0.00 | Aug 16, 2022 | tifig v0.2.2 was discovered to contain a heap-use-after-free via temInfoEntry(). |
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a resource allocation issue via operator new(unsigned long) at asan_new_delete.cpp.
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a segmentation violation via std::vector<unsigned int, std::allocator >::size() const at /bits/stl_vector.h.
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a memory leak via operator new[](unsigned long) at /asan/asan_new_delete.cpp.
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp.
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a heap-buffer overflow via __asan_memmove at /asan/asan_interceptors_memintrinsics.cpp.
- risk 0.36cvss 5.5epss 0.00
tifig v0.2.2 was discovered to contain a heap-use-after-free via temInfoEntry().