{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12742 is a high-severity command injection vulnerability in Google Cloud Looker, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12742 and fix it if it is affected.\n\nWhat it is: CVE-2025-12742 is a high-severity command injection vulnerability in Google Cloud Looker, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12742 in the wild and no public exploit code.\n\nAffected product: Google Cloud Looker. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-12742/ (Markdown: https://insights.sbomify.com/CVE-2025-12742/index.md)","id":"CVE-2025-12742","markdown":"https://insights.sbomify.com/CVE-2025-12742/index.md","name":"CVE-2025-12742","record":{"aliases":["GHSA-77vr-pq23-x7j9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Looker BI platform","requires_auth":"high_privilege","summary":"A Looker Developer can execute arbitrary commands via insecure Teradata driver parameters, requiring self-hosted instance upgrades.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GoogleCloud","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:Red","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"A Looker user with a Developer role could cause Looker to execute a malicious command, due to insecure processing of Teradata driver parameters.\n\nLooker-hosted and Self-hosted were found to be vulnerable.\nThis issue has already been mitigated for Looker-hosted instances. No user action is required for these.\n\nSelf-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted.\nThe versions below have all been updated to protect from this vulnerability. You can download these versions at the Looker download page  https://download.looker.com/ :\n  *  24.12.108+\n  *  24.18.200+\n  *  25.0.78+\n  *  25.6.65+\n  *  25.8.47+\n  *  25.12.10+\n  *  25.14+","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Remote Code Execution in Looker via Teradata JDBC Driver","id":"CVE-2025-12742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database","id":"CVE-2025-12743"},"packages":[],"prev":{"headline":"Arbitrary File Write in Denodo dialect of Looker allows Remote Code Execution","id":"CVE-2025-12741"},"products":["Looker"],"published":"2025-11-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-25","vendors":["Google Cloud"]},"summary":"A Looker Developer can execute arbitrary commands via insecure Teradata driver parameters, requiring self-hosted instance upgrades.","url":"https://insights.sbomify.com/CVE-2025-12742/"}