A memory leak (out-of-memory) in gif2rgb in util/gif2rgb.c in giflib 5.1.4 allows remote attackers trigger an out of memory exception or denial of service via a gif format file.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Giflib |
Giflib_project |
5.1.4 (including) |
5.1.4 (including) |
| Giflib |
Ubuntu |
bionic |
* |
| Giflib |
Ubuntu |
esm-infra/bionic |
* |
| Giflib |
Ubuntu |
esm-infra/xenial |
* |
| Giflib |
Ubuntu |
focal |
* |
| Giflib |
Ubuntu |
impish |
* |
| Giflib |
Ubuntu |
jammy |
* |
| Giflib |
Ubuntu |
kinetic |
* |
| Giflib |
Ubuntu |
lunar |
* |
| Giflib |
Ubuntu |
mantic |
* |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
References