Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-3598

python-pillow: Jpeg2KImagePlugin infinite loop DoS

Overview

Published
1 May 2015
Modified
6 May 2026
Medium CVE
1 Registry packages
21 OS packages
3 Linux distributions
Yes Fix available

Description

The Jpeg2KImagePlugin plugin in Pillow before 2.5.3 allows remote attackers to cause a denial of service via a crafted image.

Source: OX vulnerability database

Severity

7.5 · MEDIUM

CVSS 3.1 base score, scored by GitHub.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Weakness: CWE-399

Affected packages · 1

Packages affected by CVE-2014-3598
EcosystemPackageVulnerableFixed in
PyPI pillow <2.5.3 2.5.3

Open a package to see all its vulnerabilities.

Operating systems · 10 fixes

debian 4 releases · 1 package

fixed 4
pillow
debian fixes for CVE-2014-3598
ReleasePackageFixed in
11 pillow 2.5.3-1
12 pillow 2.5.3-1
13 pillow 2.5.3-1
14 pillow 2.5.3-1

echo 1 release · 1 package

fixed 1
pillow
echo fixes for CVE-2014-3598
ReleasePackageFixed in
pillow 2.5.3-1

openSUSE 1 release · 5 packages

fixed 5
python310-pillow python313-pillow python-pillow python3-pillow python36-pillow
openSUSE fixes for CVE-2014-3598
ReleasePackageFixed inAdvisory
Tumbleweed python310-pillow +5 10.3.0-1.1 openSUSE-SU-2024:13827-1
Tumbleweed python313-pillow +3 12.3.0-1.1 openSUSE-SU-2026:11261-1
Tumbleweed python-pillow +1 3.1.1-4.1 openSUSE-SU-2024:10567-1
Tumbleweed python3-pillow +1 3.4.2-1.1 openSUSE-SU-2024:10511-1
Tumbleweed python36-pillow +5 8.3.2-1.2 openSUSE-SU-2024:11209-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.