Filtered by vendor Rockcarry Subscriptions
Total 19 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2022-28471 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
In ffjpeg (commit hash: caade60), the function bmp_load() in bmp.c contains an integer overflow vulnerability, which eventually results in the heap overflow in jfif_encode() in jfif.c. This is due to the incomplete patch for issue 38
CVE-2021-45385 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
A Null Pointer Dereference vulnerability exits in ffjpeg d5cfd49 (2021-12-06) in bmp_load(). When the size information in metadata of the bmp is out of range, it returns without assign memory buffer to `pb->pdata` and did not exit the program. So the program crashes when it tries to access the pb->data, in jfif_encode() at jfif.c:763. This is due to the incomplete patch for CVE-2020-13438.
CVE-2021-44957 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
Global buffer overflow vulnerability exist in ffjpeg through 01.01.2021. It is similar to CVE-2020-23705. Issue is in the jfif_encode function at ffjpeg/src/jfif.c (line 708) could cause a Denial of Service by using a crafted jpeg file.
CVE-2021-44956 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
Two Heap based buffer overflow vulnerabilities exist in ffjpeg through 01.01.2021. It is similar to CVE-2020-23852. Issues that are in the jfif_decode function at ffjpeg/src/jfif.c (line 552) could cause a Denial of Service by using a crafted jpeg file.
CVE-2021-34122 1 Rockcarry 1 Ffjpeg 2024-11-21 5.5 Medium
The function bitstr_tell at bitstr.c in ffjpeg commit 4ab404e has a NULL pointer dereference.
CVE-2020-24222 1 Rockcarry 1 Ffjpeg 2024-11-21 7.8 High
Buffer Overflow vulnerability in jfif_decode() function in rockcarry ffjpeg through version 1.0.0, allows local attackers to execute arbitrary code due to an issue with ALIGN.
CVE-2020-23852 1 Rockcarry 1 Ffjpeg 2024-11-21 5.5 Medium
A heap based buffer overflow vulnerability exists in ffjpeg through 2020-07-02 in the jfif_decode(void *ctxt, BMP *pb) function at ffjpeg/src/jfif.c (line 544 & line 545), which could cause a denial of service by submitting a malicious jpeg image.
CVE-2020-23851 1 Rockcarry 1 Ffjpeg 2024-11-21 5.5 Medium
A stack-based buffer overflow vulnerability exists in ffjpeg through 2020-07-02 in the jfif_decode(void *ctxt, BMP *pb) function at ffjpeg/src/jfif.c:513:28, which could cause a denial of service by submitting a malicious jpeg image.
CVE-2020-23705 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
A global buffer overflow vulnerability in jfif_encode at jfif.c:701 of ffjpeg through 2020-06-22 allows attackers to cause a Denial of Service (DOS) via a crafted jpeg file.
CVE-2020-15470 1 Rockcarry 1 Ffjpeg 2024-11-21 5.5 Medium
ffjpeg through 2020-02-24 has a heap-based buffer overflow in jfif_decode in jfif.c.
CVE-2020-13440 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg through 2020-02-24 has an invalid write in bmp_load in bmp.c.
CVE-2020-13439 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg through 2020-02-24 has a heap-based buffer over-read in jfif_decode in jfif.c.
CVE-2020-13438 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg through 2020-02-24 has an invalid read in jfif_encode in jfif.c.
CVE-2019-19888 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
jfif_decode in jfif.c in ffjpeg through 2019-08-21 has a divide-by-zero error.
CVE-2019-19887 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
bitstr_tell at bitstr.c in ffjpeg through 2019-08-21 has a NULL pointer dereference related to jfif_encode.
CVE-2019-16352 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg before 2019-08-21 has a heap-based buffer overflow in jfif_load() at jfif.c.
CVE-2019-16351 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg before 2019-08-18 has a NULL pointer dereference in huffman_decode_step() at huffman.c.
CVE-2019-16350 1 Rockcarry 1 Ffjpeg 2024-11-21 6.5 Medium
ffjpeg before 2019-08-18 has a NULL pointer dereference in idct2d8x8() at dct.c.
CVE-2018-16781 1 Rockcarry 1 Ffjpeg 2024-11-21 N/A
ffjpeg.dll in ffjpeg before 2018-08-22 allows remote attackers to cause a denial of service (FPE signal) via a progressive JPEG file that lacks an AC Huffman table.