{"answers":{"affected":"6 open source packages ship an affected version, including typo3/cms-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-5104 in the wild and no public exploit code.","fix":"Upgrade typo3/cms-core to a fixed version for your release line: 4.2.16, 4.3.9 or 4.4.5.","what":"CVE-2010-5104 is a medium-severity vulnerability in Typo3 Typo3, published on 21 May 2012. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-5104 and fix it if it is affected.\n\nWhat it is: CVE-2010-5104 is a medium-severity vulnerability in Typo3 Typo3, published on 21 May 2012. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-5104 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-core (Packagist): affected from 4.2.0; fixed in 4.2.16\n- typo3/cms-core (Packagist): affected from 4.2.0; fixed in 4.2.16\n- typo3/cms-core (Packagist): affected from 4.3.0; fixed in 4.3.9\n- typo3/cms-core (Packagist): affected from 4.3.0; fixed in 4.3.9\n- typo3/cms-core (Packagist): affected from 4.4.0; fixed in 4.4.5\n- typo3/cms-core (Packagist): affected from 4.4.0; fixed in 4.4.5\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-2010-5104/ (Markdown: https://insights.sbomify.com/CVE-2010-5104/index.md)","id":"CVE-2010-5104","markdown":"https://insights.sbomify.com/CVE-2010-5104/index.md","name":"CVE-2010-5104","record":{"aliases":["CVE-2012-2349","GHSA-xgc2-q928-27wv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"TYPO3 CMS","requires_auth":"unknown","summary":"Remote attackers can obtain sensitive information via wildcard characters in LIKE queries when MySQL NO_BACKSLASH_ESCAPES mode is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/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 escapeStrForLike method in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly escape input when the MySQL database is set to sql_mode NO_BACKSLASH_ESCAPES, which allows remote attackers to obtain sensitive information via wildcard characters in a LIKE query.","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 Sensitive Information Disclosure via escapeStrForLike method","id":"CVE-2010-5104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2010"},"n_packages":6,"n_references":9,"next":{"headline":"Path traversal in n/a","id":"CVE-2010-5105"},"packages":[{"ecosystem":"Packagist","fixed":["4.2.16"],"introduced":["4.2.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-xgc2-q928-27wv"},{"ecosystem":"Packagist","fixed":["4.2.16"],"introduced":["4.2.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-xgc2-q928-27wv"},{"ecosystem":"Packagist","fixed":["4.3.9"],"introduced":["4.3.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-xgc2-q928-27wv"},{"ecosystem":"Packagist","fixed":["4.3.9"],"introduced":["4.3.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-xgc2-q928-27wv"},{"ecosystem":"Packagist","fixed":["4.4.5"],"introduced":["4.4.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-xgc2-q928-27wv"},{"ecosystem":"Packagist","fixed":["4.4.5"],"introduced":["4.4.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-xgc2-q928-27wv"}],"prev":{"headline":"TYPO3 SQL Injection vulnerability","id":"CVE-2010-5103"},"products":["n/a"],"published":"2012-05-21","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-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive information via wildcard characters in LIKE queries when MySQL NO_BACKSLASH_ESCAPES mode is enabled.","url":"https://insights.sbomify.com/CVE-2010-5104/"}