{"answers":{"affected":"2 open source packages ship an affected version, including typo3/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4875 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to 3.8.1 or later.","what":"CVE-2005-4875 is a high-severity vulnerability in Typo3 Typo3, published on 19 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4875 and fix it if it is affected.\n\nWhat it is: CVE-2005-4875 is a high-severity vulnerability in Typo3 Typo3, published on 19 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-4875 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected all versions; fixed in 3.8.1\n- typo3/cms (Packagist): affected all versions; fixed in 3.8.1\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-2005-4875/ (Markdown: https://insights.sbomify.com/CVE-2005-4875/index.md)","id":"CVE-2005-4875","markdown":"https://insights.sbomify.com/CVE-2005-4875/index.md","name":"CVE-2005-4875","record":{"aliases":["GHSA-xj84-6q8f-qg2r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Remote attackers can access sensitive environment variables by directly requesting the phpcheck script in TYPO3.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"TYPO3 3.8.0 and earlier allows remote attackers to obtain sensitive information via a direct request to misc/phpcheck/, which invokes the phpinfo function and prints values of unspecified environment variables.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TYPO3 Reveals Sensitive Information via Direct Request to `misc/phpcheck/`","id":"CVE-2005-4875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2005"},"n_packages":2,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-4876"},"packages":[{"ecosystem":"Packagist","fixed":["3.8.1"],"introduced":["0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-xj84-6q8f-qg2r"},{"ecosystem":"Packagist","fixed":["3.8.1"],"introduced":["0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-xj84-6q8f-qg2r"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-4874"},"products":["n/a"],"published":"2008-05-19","related":[{"cvss_score":10,"headline":"Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection","id":"CVE-2009-0258","kev_date_added":null,"published":"2009-01-22"},{"cvss_score":9.8,"headline":"Typo3 SQL injection due to faulty prepared statements","id":"CVE-2011-3583","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":9.8,"headline":"Typo3 Authentication Bypass","id":"CVE-2011-4628","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":8.8,"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":8.8,"headline":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":8.8,"headline":"Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS","id":"CVE-2020-15098","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in TYPO3 CMS","id":"CVE-2020-11067","kev_date_added":null,"published":"2020-05-13"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can access sensitive environment variables by directly requesting the phpcheck script in TYPO3.","url":"https://insights.sbomify.com/CVE-2005-4875/"}