giflib: Heap-based Buffer Overflow
CVE-2025-31344 is a high-severity heap-based buffer overflow vulnerability in giflib from openEuler, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. Affected giflib versions: 5.2.2 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.27% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of giflib you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on openeuler.org for workarounds and exact fixed builds.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H. Scored by CNA (openeuler.org).
Official description
Heap-based Buffer Overflow vulnerability in openEuler giflib on Linux. This vulnerability is associated with program files gif2rgb.C. This issue affects giflib: through 5.2.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- gitee.com/src-openeuler/giflib/pulls/54
- openwall.com/lists/oss-security/2025/04/07/3
- openwall.com/lists/oss-security/2025/04/07/4
- openwall.com/lists/oss-security/2025/04/07/5
- openwall.com/lists/oss-security/2025/04/07/6
- openwall.com/lists/oss-security/2025/04/08/1
- openwall.com/lists/oss-security/2025/04/09/5
- openwall.com/lists/oss-security/2025/04/09/7
- openwall.com/lists/oss-security/2025/04/10/1
Recent Heap-based Buffer Overflow vulnerabilities
- 7.5 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.