CVE-2024-57685
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 · uneditedAn issue in sparkshop v.1.1.7 and before allows a remote attacker to execute arbitrary code via a crafted phar file.
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 confidencesparkshop v1.1.7 and earlier contains a PHAR deserialization vulnerability where an attacker can upload or trigger a crafted PHAR archive to achieve arbitrary code execution on the server, likely through the application's file upload functionality that fails to properly validate PHAR file contents.
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<= 1.1.7CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 the installed Sparkshop versionLocate the version file or check the application header, commonly in a version.php file, composer.json, or the admin dashboard's 'About' sectionAffected if The version is 1.1.7 or earlier (any version up to and including 1.1.7)
-
Locate file upload functionalitySearch the application codebase for upload handlers, typically in controllers or modules handling user-submitted files; look for file upload forms and their processing logicAffected if The application has any file upload endpoints that accept user-provided files
-
Check if PHAR files can be uploadedAttempt to upload a test file with .phar extension through the application's upload mechanism; observe whether the upload is accepted or if the file type is validatedAffected if The upload endpoint accepts files with .phar extension without proper validation
-
Verify PHAR stream wrapper is activeCheck PHP configuration (php.ini) for the phar.stream_wrapper setting or run 'php -i | grep phar' to confirm whether the PHAR stream wrapper is enabledAffected if PHP's phar.stream_wrapper is not disabled (it is enabled by default)
-
Inspect upload validation logicReview the application's file upload validation code to determine if it performs content-type inspection, magic byte validation, or allowlist-based extension checkingAffected if The upload validation relies solely on file extension or does not explicitly block PHAR files
A user is affected if they are running Sparkshop version 1.1.7 or earlier and have any file upload functionality that does not explicitly reject PHAR files.
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.
From vendor dataImplement strict allowlist-based file type validation on all upload endpoints to reject PHAR files, disable PHP's phar.stream_wrapper if possible, and upgrade to a patched version when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57685 — 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-57685 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