Vulnerabilities > Advancemame > Advancecomp

DATE CVE VULNERABILITY TITLE RISK
2023-06-06 CVE-2023-2961 Unspecified vulnerability in Advancemame Advancecomp
A segmentation fault flaw was found in the Advancecomp package.
local
low complexity
advancemame
3.3
2022-08-29 CVE-2022-35014 Advancecomp v2.3 contains a segmentation fault.
local
low complexity
advancemame fedoraproject
5.5
2022-08-29 CVE-2022-35015 Out-of-bounds Write vulnerability in multiple products
Advancecomp v2.3 was discovered to contain a heap buffer overflow via le_uint32_read at /lib/endianrw.h.
local
low complexity
advancemame fedoraproject CWE-787
5.5
2022-08-29 CVE-2022-35016 Out-of-bounds Write vulnerability in multiple products
Advancecomp v2.3 was discovered to contain a heap buffer overflow.
local
low complexity
advancemame fedoraproject CWE-787
5.5
2022-08-29 CVE-2022-35017 Out-of-bounds Write vulnerability in multiple products
Advancecomp v2.3 was discovered to contain a heap buffer overflow.
local
low complexity
advancemame fedoraproject CWE-787
5.5
2022-08-29 CVE-2022-35018 Advancecomp v2.3 was discovered to contain a segmentation fault.
local
low complexity
advancemame fedoraproject
5.5
2022-08-29 CVE-2022-35019 Advancecomp v2.3 was discovered to contain a segmentation fault.
local
low complexity
advancemame fedoraproject
5.5
2022-08-29 CVE-2022-35020 Out-of-bounds Write vulnerability in multiple products
Advancecomp v2.3 was discovered to contain a heap buffer overflow via the component __interceptor_memcpy at /sanitizer_common/sanitizer_common_interceptors.inc.
local
low complexity
advancemame fedoraproject CWE-787
5.5
2019-02-27 CVE-2019-9210 Integer Overflow or Wraparound vulnerability in multiple products
In AdvanceCOMP 2.1, png_compress in pngex.cc in advpng has an integer overflow upon encountering an invalid PNG size, which results in an attempted memcpy to write into a buffer that is too small.
7.8
2019-02-17 CVE-2019-8383 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in multiple products
An issue was discovered in AdvanceCOMP through 2.1.
7.8