{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5217 exists.","fix":"No fix has been published for CVE-2006-5217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5217 is a high-severity SQL injection vulnerability in n/a, published on 9 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-5217 and fix it if it is affected.\n\nWhat it is: CVE-2006-5217 is a high-severity SQL injection vulnerability in n/a, published on 9 Oct 2006. 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-2006-5217 exists.\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-5217/ (Markdown: https://insights.sbomify.com/CVE-2006-5217/index.md)","id":"CVE-2006-5217","markdown":"https://insights.sbomify.com/CVE-2006-5217/index.md","name":"CVE-2006-5217","record":{"aliases":["GHSA-7cmw-qj66-jhjp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Emek Portal","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands via injection in login fields, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"emek_portal","vendor":"emek_portal"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"SQL injection vulnerability in giris_yap.asp in Emek Portal 2.1 allows remote attackers to execute arbitrary SQL commands by simultaneously injecting into the user name and pass fields in uyegiris.asp, also known as the Kullanici Adi (k_a) and Sifre (sifre) parameters.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-10-06","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-10-06","kind":"exploitdb","ref":"28768","stars":null,"title":"Emek Portal 2.1 - 'Uyegiris.asp' SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-5217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Integer overflow in n/a","id":"CVE-2006-5218"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-5216"},"products":["n/a"],"published":"2006-10-09","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)"},{"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 execute arbitrary SQL commands via injection in login fields, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2006-5217/"}