{"answers":{"affected":"2 open source packages ship an affected version, including dompdf/dompdf. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3838 exists.","fix":"Upgrade dompdf/dompdf to 2.0.0 or later.","what":"CVE-2021-3838 is a critical unsafe deserialization vulnerability in dompdf/dompdf, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-3838 and fix it if it is affected.\n\nWhat it is: CVE-2021-3838 is a critical unsafe deserialization vulnerability in dompdf/dompdf, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3838 exists.\n\nAffected packages and fixed versions:\n- dompdf/dompdf (Packagist): affected all versions; fixed in 2.0.0\n- dompdf/dompdf (Packagist): affected all versions; fixed in 2.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-3838/ (Markdown: https://insights.sbomify.com/CVE-2021-3838/index.md)","id":"CVE-2021-3838","markdown":"https://insights.sbomify.com/CVE-2021-3838/index.md","name":"CVE-2021-3838","record":{"aliases":["DEBIAN-CVE-2021-3838","DLA-3495-2","GHSA-577p-7j7h-2jgf","UBUNTU-CVE-2021-3838"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP PDF library","requires_auth":"none","summary":"An attacker can achieve remote code execution by uploading a malicious PHAR file and triggering deserialization via the phar:// protocol in dompdf.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"dompdf","vendor":"dompdf_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"DomPDF before version 2.0.0 is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the file_get_contents() function. An attacker who can upload files of any type to the server can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution, especially when DOMPdf is used with frameworks with documented POP chains like Laravel or vulnerable developer code.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"PHAR Deserialization in dompdf/dompdf","id":"CVE-2021-3838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in dpdk","id":"CVE-2021-3839"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"dompdf/dompdf","purl":null,"source":"GHSA-577p-7j7h-2jgf"},{"ecosystem":"Packagist","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"dompdf/dompdf","purl":"pkg:composer/dompdf/dompdf","source":"GHSA-577p-7j7h-2jgf"}],"prev":{"headline":"Improper Authorization in openwhyd/openwhyd","id":"CVE-2021-3837"},"products":["dompdf/dompdf"],"published":"2024-11-15","related":[{"cvss_score":10,"headline":"URI validation failure on SVG parsing. Bypass of CVE-2023-23924","id":"CVE-2023-24813","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":10,"headline":"URI validation failure on SVG parsing in Dompdf","id":"CVE-2023-23924","kev_date_added":null,"published":"2023-01-31"},{"cvss_score":9.8,"headline":"Improper Restriction of XML External Entity Reference in dompdf/dompdf","id":"CVE-2021-3902","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":9.8,"headline":"Remote code injection in dompdf/dompdf","id":"CVE-2022-28368","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":8.8,"headline":"DOMPDF Remote Code Execution","id":"CVE-2014-5013","kev_date_added":null,"published":"2020-01-10"},{"cvss_score":7.5,"headline":"Dompdf allows remote file inclusion because URI validation failure does not halt font registration","id":"CVE-2022-41343","kev_date_added":null,"published":"2022-09-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["dompdf"]},"summary":"An attacker can achieve remote code execution by uploading a malicious PHAR file and triggering deserialization via the phar:// protocol in dompdf.","url":"https://insights.sbomify.com/CVE-2021-3838/"}