{"answers":{"affected":"6 open source packages ship an affected version, including typo3/cms.","exploited":"There is no known exploitation of GHSA-ppgf-8745-8pgx in the wild and no public exploit code.","fix":"Upgrade typo3/cms to a fixed version for your release line: 7.6.30, 8.7.17 or 9.3.2.","what":"GHSA-ppgf-8745-8pgx is an unsafe deserialization vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-ppgf-8745-8pgx and fix it if it is affected.\n\nWhat it is: GHSA-ppgf-8745-8pgx is an unsafe deserialization vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-ppgf-8745-8pgx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.30\n- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.30\n- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.17\n- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.17\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.3.2\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.3.2\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/GHSA-ppgf-8745-8pgx/ (Markdown: https://insights.sbomify.com/GHSA-ppgf-8745-8pgx/index.md)","id":"GHSA-ppgf-8745-8pgx","markdown":"https://insights.sbomify.com/GHSA-ppgf-8745-8pgx/index.md","name":"GHSA-ppgf-8745-8pgx","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"low_privilege","summary":"Authenticated backend users can achieve arbitrary code execution by uploading obfuscated Phar files and triggering them via manipulated URLs.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Phar files (formerly known as \"PHP archives\") can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - \"bundle.phar\" would be valid as well as \"bundle.txt\" would be. This way, Phar files can be obfuscated as image or text file which would not be denied from being uploaded and persisted to a TYPO3 installation. Due to a missing sanitization of user input, those Phar files can be invoked by manipulated URLs in TYPO3 backend forms. A valid backend user account is needed to exploit this vulnerability. In theory the attack vector would be possible in the TYPO3 frontend as well, however no functional exploit has been identified so far.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Insecure Deserialization \u0026 Arbitrary Code Execution in TYPO3 CMS","id":"GHSA-ppgf-8745-8pgx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["7.6.30"],"introduced":["7.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-ppgf-8745-8pgx"},{"ecosystem":"Packagist","fixed":["7.6.30"],"introduced":["7.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-ppgf-8745-8pgx"},{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-ppgf-8745-8pgx"},{"ecosystem":"Packagist","fixed":["8.7.17"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-ppgf-8745-8pgx"},{"ecosystem":"Packagist","fixed":["9.3.2"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-ppgf-8745-8pgx"},{"ecosystem":"Packagist","fixed":["9.3.2"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-ppgf-8745-8pgx"}],"products":null,"published":"2024-06-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Authenticated backend users can achieve arbitrary code execution by uploading obfuscated Phar files and triggering them via manipulated URLs.","url":"https://insights.sbomify.com/GHSA-ppgf-8745-8pgx/"}