{"answers":{"affected":"6 open source packages ship an affected version, including typo3/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-1607 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2012-1607 is a medium-severity vulnerability in Typo3 Typo3, published on 4 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-1607 and fix it if it is affected.\n\nWhat it is: CVE-2012-1607 is a medium-severity vulnerability in Typo3 Typo3, published on 4 Sep 2012. 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-2012-1607 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 4.4.0 up to 4.4.13; no fix listed\n- typo3/cms (Packagist): affected from 4.4.0 up to 4.4.13; no fix listed\n- typo3/cms (Packagist): affected from 4.5.0 up to 4.5.13; no fix listed\n- typo3/cms (Packagist): affected from 4.5.0 up to 4.5.13; no fix listed\n- typo3/cms (Packagist): affected from 4.6.0 up to 4.6.6; no fix listed\n- typo3/cms (Packagist): affected from 4.6.0 up to 4.6.6; no fix listed\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-2012-1607/ (Markdown: https://insights.sbomify.com/CVE-2012-1607/index.md)","id":"CVE-2012-1607","markdown":"https://insights.sbomify.com/CVE-2012-1607/index.md","name":"CVE-2012-1607","record":{"aliases":["GHSA-q68v-vcjg-r3vp"],"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 obtain the database name via a direct request to the CLI script, exposing sensitive configuration details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","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 Command Line Interface (CLI) script in TYPO3 4.4.0 through 4.4.13, 4.5.0 through 4.5.13, 4.6.0 through 4.6.6, 4.7, and 6.0 allows remote attackers to obtain the database name via a direct request.","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 allows remote attackers to obtain the database name via a direct request","id":"CVE-2012-1607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2012"},"n_packages":6,"n_references":7,"next":{"headline":"Typo3 API XSS Vulnerabilities","id":"CVE-2012-1608"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["4.4.0"],"last_affected":["4.4.13"],"package":"typo3/cms","purl":null,"source":"GHSA-q68v-vcjg-r3vp"},{"ecosystem":"Packagist","fixed":[],"introduced":["4.4.0"],"last_affected":["4.4.13"],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-q68v-vcjg-r3vp"},{"ecosystem":"Packagist","fixed":[],"introduced":["4.5.0"],"last_affected":["4.5.13"],"package":"typo3/cms","purl":null,"source":"GHSA-q68v-vcjg-r3vp"},{"ecosystem":"Packagist","fixed":[],"introduced":["4.5.0"],"last_affected":["4.5.13"],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-q68v-vcjg-r3vp"},{"ecosystem":"Packagist","fixed":[],"introduced":["4.6.0"],"last_affected":["4.6.6"],"package":"typo3/cms","purl":null,"source":"GHSA-q68v-vcjg-r3vp"},{"ecosystem":"Packagist","fixed":[],"introduced":["4.6.0"],"last_affected":["4.6.6"],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-q68v-vcjg-r3vp"}],"prev":{"headline":"Typo3 Backend XSS Vulnerabilities","id":"CVE-2012-1606"},"products":["n/a"],"published":"2012-09-04","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-09-16","vendors":["n/a"]},"summary":"Remote attackers can obtain the database name via a direct request to the CLI script, exposing sensitive configuration details.","url":"https://insights.sbomify.com/CVE-2012-1607/"}