PillowApplication · Python
CVE-2024-28219
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 · uneditedIn _imagingcms.c in Pillow before 10.3.0, a buffer overflow exists because strcpy is used instead of strncpy.
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 · high confidenceA buffer overflow vulnerability exists in Pillow's _imagingcms.c extension where the use of unbounded strcpy() instead of bounds-checked strncpy() allows potential memory corruption when handling strings in the color management system (CMS) module.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PillowApplication
< 10.3.0
Debian LinuxOperating system
= 10.0CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Pillow versionRun 'pip show pillow' or 'python -c "import PIL; print(PIL.__version__)"' to get the installed version numberAffected if Version is lower than 10.3.0 (e.g., 10.2.0, 10.1.0, etc.)
-
Verify _imagingcms extension is presentCheck if the _imagingcms C extension module exists in the Pillow installation directory or attempt to import it with 'python -c "from PIL import _imagingcms"'Affected if The module imports successfully without error, indicating the vulnerable C extension is loaded
-
Confirm CMS functionality is accessibleRun 'python -c "from PIL import ImageCms; print(dir(ImageCms))"' to list available CMS functionsAffected if The ImageCms module loads and exposes CMS functions (e.g., get profiledata, getcolorspace, getopenformat)
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped10.3.0
Upgrade Pillow to version 10.3.0 or later which replaces strcpy with safe strncpy usage. If immediate upgrade is not feasible, recompile the _imagingcms C extension with bounds-checked string functions.
Pillow 10.3.0
- Verify current Pillow version by running 'pip show pillow' or checking your dependencies
- Upgrade Pillow to version 10.3.0 or later using 'pip install --upgrade Pillow>=10.3.0'
- Verify the installation was successful by running 'pip show pillow' and confirming the version number
- If using a package manager (e.g., apt, yum, dnf), run 'pip install --upgrade Pillow==10.3.0' or check for distribution-specific security updates
- Re-run any automated tests to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pillow
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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