Source: advancecomp X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security
Hi, The following vulnerabilities were published for advancecomp. Multiple issues in advancement, I suppose none of these have actually been forwarded upstream by the reporter: CVE-2022-35020[0]: | Advancecomp v2.3 was discovered to contain a heap buffer overflow via | the component __interceptor_memcpy at | /sanitizer_common/sanitizer_common_interceptors.inc. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35020.md CVE-2022-35019[1]: | Advancecomp v2.3 was discovered to contain a segmentation fault. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35019.md CVE-2022-35018[2]: | Advancecomp v2.3 was discovered to contain a segmentation fault. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35018.md CVE-2022-35017[3]: | Advancecomp v2.3 was discovered to contain a heap buffer overflow. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35017.md CVE-2022-35016[4]: | Advancecomp v2.3 was discovered to contain a heap buffer overflow. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35016.md CVE-2022-35015[5]: | Advancecomp v2.3 was discovered to contain a heap buffer overflow via | le_uint32_read at /lib/endianrw.h. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35015.md CVE-2022-35014[6]: | Advancecomp v2.3 contains a segmentation fault. https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35014.md If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-35020 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35020 [1] https://security-tracker.debian.org/tracker/CVE-2022-35019 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35019 [2] https://security-tracker.debian.org/tracker/CVE-2022-35018 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35018 [3] https://security-tracker.debian.org/tracker/CVE-2022-35017 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35017 [4] https://security-tracker.debian.org/tracker/CVE-2022-35016 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35016 [5] https://security-tracker.debian.org/tracker/CVE-2022-35015 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35015 [6] https://security-tracker.debian.org/tracker/CVE-2022-35014 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35014 Please adjust the affected versions in the BTS as needed.
