Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-5hw4-m7f3-hhx8

CRITICAL

TCPDF vulnerable to attackers triggering deserialization of arbitrary data

Also known asCVE-2018-17057
Published
Oct 6, 2022
Updated
Feb 16, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
2 known

EPSS Exploitation Probability

via FIRST.org ↗
26.2%probability of exploitation in next 30 days
Moderate Risk98th percentile-25.95%
18.2%32.4%46.5%60.6%52.7%26.2%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
🐘tecnickcom/tcpdf🐘fooman/tcpdf🐘la-haute-societe/tcpdf🐘spoonity/tcpdf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in TCPDF before 6.2.22. Attackers can trigger deserialization of arbitrary data via the phar:// wrapper.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttecnickcom/tcpdfall versions6.2.22
🐘Packagistfooman/tcpdfall versions6.2.22
🐘Packagistla-haute-societe/tcpdfall versions6.2.22
🐘Packagistspoonity/tcpdfall versions6.2.22
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46634webappsphp

LimeSurvey < 3.16 - Remote Code Execution

by q3rv0 · Apr 2, 2019

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tecnickcom/tcpdf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update tecnickcom/tcpdf to 6.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5hw4-m7f3-hhx8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5hw4-m7f3-hhx8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5hw4-m7f3-hhx8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in TCPDF before 6.2.22. Attackers can trigger deserialization of arbitrary data via the `phar://` wrapper.
O3 Security · Impact-Aware SCA

Is GHSA-5hw4-m7f3-hhx8 in your dependencies?

O3 detects GHSA-5hw4-m7f3-hhx8 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.