Source: freeimage X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security
Hi, The following vulnerabilities were published for freeimage. They are all only published at https://github.com/Ruanxingzhi/vul-report/tree/master/freeimage-r1909 and don't appear to be forwarded upstream yet. CVE-2024-28562[0]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | Imf_2_2::copyIntoFrameBuffer() component when reading images in EXR | format. CVE-2024-28563[1]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the Imf_2_2::DwaCompressor::Classifier::Classifier() function | when reading images in EXR format. CVE-2024-28564[2]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the Imf_2_2::CharPtrIO::readChars() function when reading images | in EXR format. CVE-2024-28565[3]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the psdParser::ReadImageData() function when reading images in | PSD format. CVE-2024-28566[4]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | AssignPixel() function when reading images in TIFF format. CVE-2024-28567[5]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the FreeImage_CreateICCProfile() function when reading images in | TIFF format. CVE-2024-28568[6]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the read_iptc_profile() function when reading images in TIFF | format. CVE-2024-28569[7]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | Imf_2_2::Xdr::read() function when reading images in EXR format. CVE-2024-28570[8]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the processMakerNote() function when reading images in JPEG | format. CVE-2024-28571[9]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the fill_input_buffer() function when reading images in JPEG | format. CVE-2024-28572[10]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the FreeImage_SetTagValue() function when reading images in JPEG | format. CVE-2024-28573[11]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the jpeg_read_exif_profile() function when reading images in | JPEG format. CVE-2024-28574[12]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the opj_j2k_copy_default_tcp_and_create_tcd() function when | reading images in J2K format. CVE-2024-28574[13]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the opj_j2k_copy_default_tcp_and_create_tcd() function when | reading images in J2K format. CVE-2024-28575[14]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the opj_j2k_read_mct() function when reading images in J2K | format. CVE-2024-28576[15]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the opj_j2k_tcp_destroy() function when reading images in J2K | format. CVE-2024-28577[16]: | Null Pointer Dereference vulnerability in open source FreeImage | v.3.19.0 [r1909] allows a local attacker to cause a denial of | service (DoS) via the jpeg_read_exif_profile_raw() function when | reading images in JPEG format. CVE-2024-28578[17]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | Load() function when reading images in RAS format. CVE-2024-28579[18]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to cause a denial of service (DoS) | via the FreeImage_Unload() function when reading images in HDR | format. CVE-2024-28580[19]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | ReadData() function when reading images in RAS format. CVE-2024-28581[20]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | _assignPixel<>() function when reading images in TARGA format. CVE-2024-28582[21]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | rgbe_RGBEToFloat() function when reading images in HDR format. CVE-2024-28583[22]: | Buffer Overflow vulnerability in open source FreeImage v.3.19.0 | [r1909] allows a local attacker to execute arbitrary code via the | readLine() function when reading images in XPM format. CVE-2024-28584[23]: | Null Pointer Dereference vulnerability in open source FreeImage | v.3.19.0 [r1909] allows a local attacker to cause a denial of | service (DoS) via the J2KImageToFIBITMAP() function when reading | images in J2K format. 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-2024-28562 https://www.cve.org/CVERecord?id=CVE-2024-28562 [1] https://security-tracker.debian.org/tracker/CVE-2024-28563 https://www.cve.org/CVERecord?id=CVE-2024-28563 [2] https://security-tracker.debian.org/tracker/CVE-2024-28564 https://www.cve.org/CVERecord?id=CVE-2024-28564 [3] https://security-tracker.debian.org/tracker/CVE-2024-28565 https://www.cve.org/CVERecord?id=CVE-2024-28565 [4] https://security-tracker.debian.org/tracker/CVE-2024-28566 https://www.cve.org/CVERecord?id=CVE-2024-28566 [5] https://security-tracker.debian.org/tracker/CVE-2024-28567 https://www.cve.org/CVERecord?id=CVE-2024-28567 [6] https://security-tracker.debian.org/tracker/CVE-2024-28568 https://www.cve.org/CVERecord?id=CVE-2024-28568 [7] https://security-tracker.debian.org/tracker/CVE-2024-28569 https://www.cve.org/CVERecord?id=CVE-2024-28569 [8] https://security-tracker.debian.org/tracker/CVE-2024-28570 https://www.cve.org/CVERecord?id=CVE-2024-28570 [9] https://security-tracker.debian.org/tracker/CVE-2024-28571 https://www.cve.org/CVERecord?id=CVE-2024-28571 [10] https://security-tracker.debian.org/tracker/CVE-2024-28572 https://www.cve.org/CVERecord?id=CVE-2024-28572 [11] https://security-tracker.debian.org/tracker/CVE-2024-28573 https://www.cve.org/CVERecord?id=CVE-2024-28573 [12] https://security-tracker.debian.org/tracker/CVE-2024-28574 https://www.cve.org/CVERecord?id=CVE-2024-28574 [13] https://security-tracker.debian.org/tracker/CVE-2024-28574 https://www.cve.org/CVERecord?id=CVE-2024-28574 [14] https://security-tracker.debian.org/tracker/CVE-2024-28575 https://www.cve.org/CVERecord?id=CVE-2024-28575 [15] https://security-tracker.debian.org/tracker/CVE-2024-28576 https://www.cve.org/CVERecord?id=CVE-2024-28576 [16] https://security-tracker.debian.org/tracker/CVE-2024-28577 https://www.cve.org/CVERecord?id=CVE-2024-28577 [17] https://security-tracker.debian.org/tracker/CVE-2024-28578 https://www.cve.org/CVERecord?id=CVE-2024-28578 [18] https://security-tracker.debian.org/tracker/CVE-2024-28579 https://www.cve.org/CVERecord?id=CVE-2024-28579 [19] https://security-tracker.debian.org/tracker/CVE-2024-28580 https://www.cve.org/CVERecord?id=CVE-2024-28580 [20] https://security-tracker.debian.org/tracker/CVE-2024-28581 https://www.cve.org/CVERecord?id=CVE-2024-28581 [21] https://security-tracker.debian.org/tracker/CVE-2024-28582 https://www.cve.org/CVERecord?id=CVE-2024-28582 [22] https://security-tracker.debian.org/tracker/CVE-2024-28583 https://www.cve.org/CVERecord?id=CVE-2024-28583 [23] https://security-tracker.debian.org/tracker/CVE-2024-28584 https://www.cve.org/CVERecord?id=CVE-2024-28584 Please adjust the affected versions in the BTS as needed.
