CVE-2024-48514
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 · uneditedphp-heic-to-jpg <= 1.0.5 is vulnerable to code injection (fixed in 1.0.6). An attacker who can upload heic images is able to execute code on the remote server via the file name. As a result, the CIA is no longer guaranteed. This affects php-heic-to-jpg 1.0.5 and below.
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 confidenceCode injection vulnerability in php-heic-to-jpg <= 1.0.5 allows remote code execution via malicious HEIC file names during upload. An attacker can inject and execute arbitrary commands on the server by including malicious code in the uploaded filename.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify php-heic-to-jpg installationSearch for php-heic-to-jpg in your project dependencies (check composer.json, composer.lock, or vendor directory). If used as a library, locate the package directory.Affected if The package is present in your environment and processes user-uploaded HEIC files.
-
Determine installed versionCheck the version number in composer.json, composer.lock, or the package's composer.json file within vendor/. Compare against the affected range: versions 1.0.5 and below.Affected if The installed version is 1.0.5 or lower.
-
Verify upload functionality is in useInspect your codebase for instances where php-heic-to-jpg functions are called to process uploaded files. Look for file upload handlers that accept HEIC files from users.Affected if Your application uses this library to process HEIC file uploads from users or external sources.
-
Examine filename handling in upload codeReview the code that handles uploaded HEIC filenames. Check if the filename is passed directly to shell commands, exec(), system(), or similar functions without sanitization.Affected if Uploaded filenames are used in shell execution contexts without validation or sanitization.
-
Check for filename validation controlsSearch for input validation routines that sanitize or restrict characters in uploaded filenames before processing. Look for allowlists, regex filters, or safe filename handling.Affected if No filename sanitization exists, or the validation can be bypassed by malicious characters in the HEIC filename.
You are affected if php-heic-to-jpg version 1.0.5 or lower is installed AND your application uses it to process HEIC file uploads without proper filename sanitization before shell execution.
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 · scopedUpgrade to php-heic-to-jpg version 1.0.6 or later. Until patched, implement strict filename sanitization for uploads and restrict executable permissions on upload directories.
1.0.6
- 1. Identify the currently installed version of php-heic-to-jpg by checking your project's composer.json, vendor directory, or dependency lock file
- 2. If the current version is 1.0.5 or below, plan an upgrade to version 1.0.6 or later
- 3. Update the dependency using your package manager (e.g., composer require php-heic-to-jpg:^1.0.6 or composer update php-heic-to-jpg)
- 4. Verify the upgrade was successful by checking the installed version
- 5. Test that heic to jpg conversion functionality still works correctly after the upgrade
- 6. Review the application's file upload handling to ensure proper sanitization of filenames, even after applying the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48514 — 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-48514 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