CVE intelligence and bounded remediation
CVE-2023-41330 — knplabs/knp-snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page
knplabs/knp-snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. ## Issue On March 17th the vulnerability CVE-2023-28115 was disclosed, allowing an attacker to gain remote code execution through PHAR deserialization. Version 1.4.2 added a check `if (\strpos($filename, 'phar://') === 0)` in the `prepareOutput` function to resolve this CVE, however if the user is able to control the second parameter of the `generateFromHtml()` function of Snappy, it will then be passed as the `$filename` parameter in the `prepareOutput()` function. In the original vulnerability, a file name with a `phar://` wrapper could be sent to the `fileExists()` function, equivalent to the `file_exists()` PHP function. This allowed users to trigger a deserialization on arbitrary PHAR files. To fix this issue, the string is now passed to the `strpos()` function and if it starts with `phar://`, an exception is raised. However, PHP wrappers being case insensitive, this patch can be bypassed using `PHAR://` instead of `phar://`. A successful exploitation of this vulnerability allows executing arbitrary code and accessing the underlying filesystem. The attacker must be ab…
- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Published
- 2023-09-06
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-502
Affected products
- knplabs / snappy
Matched remediation archetype
Unsafe deserialization and object reconstruction
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory serialization formats accepted from requests, queues, caches, files, cookies, and cross-service messages.
- Trace whether untrusted input can select classes, types, callbacks, constructors, or object hooks during decoding.
- Identify signing, schema validation, trust-boundary, and compatibility settings for each decoder.
Remediate safely
- Replace native object deserialization with a data-only format and explicit schema validation.
- If replacement is not immediate, use a safe decoder with a minimal type allowlist and disable polymorphic or executable hooks.
- Update the affected library and add inert tests for unknown types, extra fields, malformed nesting, and unsigned data.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.