{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-2547 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-2547 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-2547 is a critical command injection vulnerability in n/a, published on 23 May 2006. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-2547 and fix it if it is affected.\n\nWhat it is: CVE-2006-2547 is a critical command injection vulnerability in n/a, published on 23 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-2547 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2006-2547/ (Markdown: https://insights.sbomify.com/CVE-2006-2547/index.md)","id":"CVE-2006-2547","markdown":"https://insights.sbomify.com/CVE-2006-2547/index.md","name":"CVE-2006-2547","record":{"aliases":["GHSA-hq2w-ggp5-cvj4"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SAP Informix database","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary commands via insecure environment variable handling in the sapdba command.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sapdba","vendor":"sap"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in the sapdba command in SAP with Informix before 700, and 700 up to patch 100, allows local users to execute arbitrary commands via unknown vectors related to \"insecure environment variable\" handling.","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":"Command injection in n/a","id":"CVE-2006-2547","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2006"},"n_packages":0,"n_references":9,"next":{"headline":"Command injection in n/a","id":"CVE-2006-2548"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-2546"},"products":["n/a"],"published":"2006-05-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"Local attackers can execute arbitrary commands via insecure environment variable handling in the sapdba command.","url":"https://insights.sbomify.com/CVE-2006-2547/"}