{"answers":{"affected":"6 open source packages ship an affected version, including typo3/cms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0815 exists.","fix":"Upgrade typo3/cms to a fixed version for your release line: 4.0.12, 4.1.10 or 4.2.6.","what":"CVE-2009-0815 is a medium-severity vulnerability in Typo3 Typo3, published on 5 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-0815 and fix it if it is affected.\n\nWhat it is: CVE-2009-0815 is a medium-severity vulnerability in Typo3 Typo3, published on 5 Mar 2009. 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-2009-0815 exists.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 3.3; fixed in 4.0.12\n- typo3/cms (Packagist): affected from 3.3; fixed in 4.0.12\n- typo3/cms (Packagist): affected from 4.1; fixed in 4.1.10\n- typo3/cms (Packagist): affected from 4.1; fixed in 4.1.10\n- typo3/cms (Packagist): affected from 4.2; fixed in 4.2.6\n- typo3/cms (Packagist): affected from 4.2; fixed in 4.2.6\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-2009-0815/ (Markdown: https://insights.sbomify.com/CVE-2009-0815/index.md)","id":"CVE-2009-0815","markdown":"https://insights.sbomify.com/CVE-2009-0815/index.md","name":"CVE-2009-0815","record":{"aliases":["GHSA-c22j-84c7-cm77"],"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 read arbitrary files by exploiting a hash secret leak in TYPO3's jumpUrl mechanism error messages.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The jumpUrl mechanism in class.tslib_fe.php in TYPO3 3.3.x through 3.8.x, 4.0 before 4.0.12, 4.1 before 4.1.10, 4.2 before 4.2.6, and 4.3alpha1 leaks a hash secret (juHash) in an error message, which allows remote attackers to read arbitrary files by including the hash in a request.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2009-02-10","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2009-02-10","kind":"exploitdb","ref":"8038","stars":null,"title":"TYPO3 \u003c 4.0.12/4.1.10/4.2.6 - 'jumpUrl' Remote File Disclosure"},{"date":"2009-02-10","kind":"metasploit","ref":"auxiliary/admin/http/typo3_sa_2009_002","stars":null,"title":"Typo3 sa-2009-002 File Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"TYPO3 leaks a hash secret in an error message","id":"CVE-2009-0815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2009"},"n_packages":6,"n_references":4,"next":{"headline":"Typo3 Backend XSS Vulnerability","id":"CVE-2009-0816"},"packages":[{"ecosystem":"Packagist","fixed":["4.0.12"],"introduced":["3.3"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-c22j-84c7-cm77"},{"ecosystem":"Packagist","fixed":["4.0.12"],"introduced":["3.3"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-c22j-84c7-cm77"},{"ecosystem":"Packagist","fixed":["4.1.10"],"introduced":["4.1"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-c22j-84c7-cm77"},{"ecosystem":"Packagist","fixed":["4.1.10"],"introduced":["4.1"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-c22j-84c7-cm77"},{"ecosystem":"Packagist","fixed":["4.2.6"],"introduced":["4.2"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-c22j-84c7-cm77"},{"ecosystem":"Packagist","fixed":["4.2.6"],"introduced":["4.2"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-c22j-84c7-cm77"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-0814"},"products":["n/a"],"published":"2009-03-05","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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can read arbitrary files by exploiting a hash secret leak in TYPO3's jumpUrl mechanism error messages.","url":"https://insights.sbomify.com/CVE-2009-0815/"}