Please help me
Hello. I'm looking for GAT-D software. Could you tell me for link? Best Regards. Alexander
Please help me purchase the program GAT -D V01.00.01.0004
Is FreeImage still active?
CVE-2025-65803: Heap Buffer Overflow DoS Vulnerability in FreeImage (psdParser::ReadImageData)
Nose
**gwergewg ** You are wrong - the FreeImage library is a dynamically plug-in module, in this case a DLL, and like any DLL it is launched in the process of the calling module, usually it is a GUI or console program and in this archive it is in the \FreeImage\Dist\x32\ and \FreeImage\Dist\x64\ directories. Yes, it cannot be used directly because, like any DLL, it has a special call format (API), but if we have an application that can work with it and uses an older version of the library, and if the...
**gwergewg ** You are wrong - the FreeImage library is a dynamically plug-in module, in this case a DLL, and like any DLL it is launched in the process of the calling module, usually it is a GUI or console program and in this archive it is in the \FreeImage\Dist\x32\ and \FreeImage\Dist\x64\ directories. Yes, it cannot be used directly because, like any DLL, it has a special call format (API), but if we have an application that can work with it and uses an older version of the library, and if the...
Hi there, If there is not a .exe 32b or a .exe 64b fille in the folder you should not call it win32/win64 unlike linux windows programs come with exe filles....most windows users dont use compillers nor should they if marked with Win32Win64 can you update and actualy include the exe fille or remove the deceptive download link thx in advance
GCC 14 build fixes
I found the source of my problem. The image contains EXIF orientation metadata. It was originally landscape, then it was flipped (portrait).
I found the source of my problem. The image contains EXIF orientation metadata. It was originally landscape, then it was flipped (portrait).
Arch-Linux has removed FreeImage from their repositories. It still is available on AUR, though. Other Linux Distros also have removed FreeInmage Lib. A comment on AUR mentioned that there is FreeImage Re(surrected) to be found here: https://github.com/agruzdev/FreeImageRe but that it is not packaged so far.
GetWidth / GetHeight : height and width reversed
Hi, Are there any plans, or has anyone added support for TIFF > 4GB? Cheers
Hello, can you fix the bug where saving as DDS fails, such as when saving as DDS in BMP format
Hello, could you please fix the bug where saving in other formats as DDS fails, such as when saving in bmp format as DDS
FreeImage_Save fails to save in DDS file format
I want to do something like this with the same FIBITMAP I guess FreeImage.GetBits is read-only, so when I get the Bits, I do read-only operations on the Bits, so I can add a read lock. I guess FreeImage.Save is also read-only, so I can add a read lock when I call FreeImage. This way, the above two operations can be done in different threads! Is my idea correct? How do I identify which interfaces are read-only? @drolon
I want to do something like this with the same FIBITMAP I guess FreeImage.GetBits is read-only, so when I get the Bits, I do read-only operations on the Bits, so I can add a read lock. I guess FreeImage.Save is also read-only, so I can add a read lock when I call FreeImage. This way, the above two operations can be done in different threads! Is my idea correct? How do I identify which interfaces are read-only?
hi, is it yet possible to read the layers of a multilayer exr and then save back out to a multilayer EXR with freeimage?
See https://sourceforge.net/p/freeimage/patches/151/
Hi Mihail! line_s and line_t must be size_t to prevent wraparound into negative values. pitch and height could remain as int(though why I can't imagine).
Please add Apple Silicon M1/M2 support
Should be resolved by r1906 and r1907.
Hi Ron, see https://sourceforge.net/p/freeimage/patches/137/ hope this help, Hervé
Any news on integratin avif?
Anything new regarding the avif-support?
Binaries for HEIF plugin?
Hi there, Is AVIF support coming? Is that in the cards? Thanks R
Update with patches and fixes any time soon ?
[Workaround] Build with GCC 14 fails with `gzlib.c:14:17: error: implicit declaration of function ‘lseek’; did you mean ‘fseek’? [-Wimplicit-function-declaration]`.
Is there a simpler way to render images with transparency (alpha or a designated transparent color) obtained from FreeImage? There seems to be one; we might call GDIplus. Below I whipped a subroutine up, containing all the GDIplus calls involved (extracted from a bigger program elsewhere). All you have to do is to add declarations of the stated Subs/Functions, the associated Enums and Types. If you use FreeImage often, it is worthwhile to spend a little time on it. The subroutine is supposed to be...
Is there a simpler way to render images with transparency (alpha or a designated transparent color) obtained from FreeImage? There seems to be one; we might call GDIplus. Below I whipped a subroutine up, containing all the GDIplus calls involved (extracted from a bigger program elsewhere). All you have to do is to add declarations of the stated Subs/Functions, the associated Enums and Types. If you use FreeImage often, it is worthwhile to spend a little time on it. The subroutine is supposed to be...
Is there a simpler way to render images with transparency (alpha or a designated transparent color) obtained from FreeImage? There seems to be one; we might call GDIplus. Below I whipped a subroutine up, containing all the GDIplus calls involved (extracted from a bigger program elsewhere). All you have to do is to add declarations of the stated Subs/Functions, the associated Enums and Types. If you use FreeImage often, it is worthwhile to spend a little time on it. The subroutine is supposed to be...
Is there a simpler way to render images with transparency (alpha or a designated transparent color) obtained from FreeImage? There seems to be one; we might call GDIplus. Below I whipped a subroutine up, containing all the GDIplus calls involved (extracted from a bigger program elsewhere). All you have to do is to add declarations of the stated Subs/Functions, the associated Enums and Types. If you use FreeImage often, it is worthwhile to spend a little time on it. The subroutine is supposed to be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) transparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." To run AlphaBlend, both destination and source DIBs must be 32-BPP,...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) transparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." To run AlphaBlend, both destination and source DIBs must be 32-BPP,...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about merely relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be...
I believe you can forget about relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be 32-BPP,...
I believe you can forget about relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be 32-BPP,...
I believe you can forget about relying on FreeImage_PaintTransparent. It is just too good to be True. There are remarks made by Carsten Klein, the great author, notably " Since this is a wrapper for the Windows GDI function AlphaBlend(), 32-bit images, containing alpha (or per-pixel) ransparency, must be premultiplied for alpha transparent regions to actually show transparent. See MSDN help on the AlphaBlend() function. ...." Note: To run AlphaBlend, both destination and source DIBs must be 32-BPP,...
Description When saving a .exr file using FreeImage with a FIBITMAP of type FIT_RGBF and the EXR_FLOAT flag, the resulting file is saved with a 16-bit depth per channel instead of the expected 32-bit float depth. This behavior persists even though the EXR_FLOAT flag is explicitly passed to the FreeImage_Save function. My code: Click to expand code #include <FreeImage.h> #include <iostream> #include <string> FIBITMAP* CreateTestImage(unsigned width, unsigned height) { FIBITMAP* bitmap = FreeImage_AllocateT(FIT_RGBF,...
I found another reason to support what I said above "Carson mentioned v 5.0 in another thread; I hope that the 1st thing the v 5.0 developers should do is to go back to v 3.16 code as far as PNG is concerned (see 1st paragraph).", see https://sourceforge.net/p/freeimage/discussion/36111/thread/26659aabc9/ The above thread pointed out the following: Using Freeimage v3.18, the " FreeImage.GetICCProfileEx(dib).Data;" byte values is randomly incorrect .... .... running the same method using FreeImage...
I found another reason to support what I said above "Carson mentioned v 5.0 in another thread; I hope that the 1st thing the v 5.0 developers should do is to go back to v 3.16 code as far as PNG is concerned (see 1st paragraph).", see https://sourceforge.net/p/freeimage/discussion/36111/thread/26659aabc9/
Giving DeepL a chance (don't know how good that one is, because: Je ne comprends rien): Dans Windows, un processus recherche les bibliothèques partagées requises (par exemple les DLL) dans plusieurs endroits, et ce dans un ordre bien défini. L'un de ces endroits est le répertoire dans lequel se trouve le module qui charge la bibliothèque (DLL). Ainsi, placer la FreeImage.dll dans le dossier de votre projet n'est pas une mauvaise idée. Lorsque vous compilez votre projet en un exécutable (par exemple...
Bonjour Mathieu, (unfortunately, my French is much too bad for writing such texts, so I hope you could translate that back to French) in Windows, a process searches required shared libraries (e.g. DLLs) at several places in a well defined order. One of these places is the directory, in which the module that is loading the library (DLL) is located. So, putting the FreeImage.dll into your project folder is basically not a bad idea. When you compile your project into an executable (e.g. Project1.exe),...
Please show me how did you call FreeImage which resulted in being told that FreeImage.dll could not be found.
Translated into English via Google Translate: Hello, I want to use FreeImage in my VB6 projects, but it always tells me that it can't find FreeImage.dll even though I put the FreeImage.dll dll (32 bits) in my project folder?
Potential regression in LoadPixelDataRLE8 since 3.19.0
Bonjour, Je souhaite utiliser FreeImage dans mes projet en VB6, mais il me dit toujours qu'il ne trouve pas FreeImage.dll alors que j'ai bien mis la dll FreeImage.dll (32 bits) dans mon dossier de projet ?
This is probably a duplicate of #355 (it is currently private, and I don't have access to it)
CVE-2024-31570: stack-based buffer overflow in the PluginXPM.cpp Load function when handling XPM files
CVE-2024-28584: Null Pointer Dereference in J2KImageToFIBITMAP()
CVE-2024-28583: Buffer Overflow in readLine() when reading XPM images
CVE-2024-28582: Buffer Overflow in rgbe_RGBEToFloat()
CVE-2024-28581: Buffer Overflow in _assignPixel() relating to TARGA images
CVE-2024-28580: Buffer Overflow in ReadData() when reading a RAS image
CVE-2024-28579: Buffer Overflow in FreeImage_Unload() when handling an HDR file
CVE-2024-28578: Buffer Overflow in Load() when reading a RAS file
CVE-2024-28577: Null Pointer Dereference in jpeg_read_exif_profile_raw()
CVE-2024-28576: Buffer Overflow in opj_j2k_tcp_destroy()
CVE-2024-28575: Buffer Overflow in opj_j2k_read_mct()
CVE-2024-28574: Buffer Overflow in opj_j2k_copy_default_tcp_and_create_tcd()
CVE-2024-28573: Buffer Overflow in jpeg_read_exif_profile()
CVE-2024-28572: Buffer Overflow in FreeImage_SetTagValue()
CVE-2024-28571: Buffer Overflow in fill_input_buffer()
CVE-2024-28570: Buffer Overflow in processMakerNote()
CVE-2024-28569: Buffer Overflow in Imf_2_2::Xdr::read()
CVE-2024-28568: Buffer Overflow in read_iptc_profile()
CVE-2024-28567: Buffer Overflow in FreeImage_CreateICCProfile() 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. The aim of this ticket is to forward upstream the vulnerabilities published at [https://github.com/Ruanxingzhi/vul-report/tree/master/freeimage-r1909](https://github.com/Ruanxingzhi/vul-report/tree/master/freeimage-r1909). Please see there for more details.CVE-2024-28567: Buffer Overflow in FreeImage_CreateICCProfile()
CVE-2024-28566: Buffer Overflow in AssignPixel() when reading TIFF images
CVE-2024-28565: Buffer Overflow in psdParser::ReadImageData() when reading PSD images
CVE-2024-28564: Buffer Overflow in Imf_2_2::CharPtrIO::readChars() when reading images in EXR format
CVE-2024-28563: Buffer Overflow in Imf_2_2::DwaCompressor::Classifier::Classifier()
CVE-2024-28562: buffer overflow in Imf_2_2::copyIntoFrameBuffer()
Fix for #362 (CVE-2023-47997)
CVE-2023-47997: infinite loop in PluginTIFF.cpp::Load
CVE-2023-47996: integer overflow in Exif.cpp::jpeg_read_exif_dir
Fix for #360 (CVE-2023-47995)
CVE-2023-47995: memory allocation with excessive size value in BitmapAccess.cpp::FreeImage_AllocateBitmap
CVE-2023-47994: integer overflow in LoadPixelDataRLE4 function in PluginBMP.cpp
CVE-2023-47993: buffer out-of-bound read vulnerability in Exif.cpp::ReadInt32 in FreeImage 3.18.0
CVE-2023-47992: integer overflow in FreeImageIO.cpp::_MemoryReadProc
CVE-2024-9029 has been assigned to this issue. The fix for this issue should also address #356 at the same time.
Heap buffer overflow in read_iptc_profile() from Source/Metadata/IPTC.cpp:95
Maybe Homebrew can help? https://brew.sh/ https://formulae.brew.sh/formula/freeimage#default
What's new