dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-31344

HIGH · 7.3 CVSS v3.1 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow in gif2rgb.C when processing GIF image data for conversion to RGB format. The vulnerability allows memory corruption during the conversion process, potentially enabling arbitrary code execution or denial of service via specially crafted GIF files.

MitigationUpdate giflib to version 5.2.2 or later if available, or apply vendor-provided patches. Until a fix is available, restrict processing of untrusted GIF files and validate input file sizes before conversion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if giflib is installed
    Run 'giflib' version check: on Debian/Ubuntu use 'dpkg -l | grep giflib' or check for presence of 'gif2rgb' binary with 'which gif2rgb' or 'ls -la /usr/bin/gif2rgb'
    Affected if giflib or gif2rgb binary is found on the system
  2. Determine the installed giflib version
    Run 'gif2rgb -v' or check package version: 'dpkg -l libgif-dev' on Debian-based systems, 'rpm -qa | grep gif' on RHEL-based systems, or inspect the binary with 'strings /usr/bin/gif2rgb | grep -i version'
    Affected if Version is present and is below 5.2.2, or version cannot be determined (older unpatched installation)
  3. Check if gif2rgb is invoked in your environment
    Search scripts, cron jobs, or applications that call gif2rgb: grep -r 'gif2rgb' /etc /opt /home or review application code that processes GIF files
    Affected if gif2rgb is actively used to convert GIF files to RGB format
  4. Identify source of GIF files being processed
    Review logs, file processing pipelines, or user upload mechanisms that feed GIFs to gif2rgb, and determine if they originate from untrusted or external sources
    Affected if GIF files from untrusted or external sources are processed by gif2rgb

You are affected if giflib version is below 5.2.2 AND gif2rgb is used to process GIF files, especially those from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update giflib to version 5.2.2 or later if available, or apply vendor-provided patches. Until a fix is available, restrict processing of untrusted GIF files and validate input file sizes before conversion.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31344 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data