{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6593 exists.","fix":"No fix has been published for CVE-2008-6593 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-6593 is a high-severity SQL injection vulnerability in Sqlite Sqlite, published on 3 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-6593 and fix it if it is affected.\n\nWhat it is: CVE-2008-6593 is a high-severity SQL injection vulnerability in Sqlite Sqlite, published on 3 Apr 2009. 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-2008-6593 exists.\n\nAffected product: Sqlite Sqlite. 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-2008-6593/ (Markdown: https://insights.sbomify.com/CVE-2008-6593/index.md)","id":"CVE-2008-6593","markdown":"https://insights.sbomify.com/CVE-2008-6593/index.md","name":"CVE-2008-6593","record":{"aliases":["GHSA-482p-ffx2-mg3c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LightNEasy SQLite","requires_auth":"none","summary":"Remote attackers can inject arbitrary PHP code via SQL injection in the dlid parameter, leading to code execution and data modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lightneasy","vendor":"lightneasy"},{"product":"sqlite","vendor":"sqlite"}],"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":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in LightNEasy/lightneasy.php in LightNEasy SQLite 1.2.2 and earlier allows remote attackers to inject arbitrary PHP code into comments.dat via the dlid parameter to index.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2008-04-15","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2008-04-15","kind":"exploitdb","ref":"5452","stars":null,"title":"LightNEasy sqlite / no database 1.2.2 - Multiple Vulnerabilities"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2008-6593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sqlite:sqlite","products":["sqlite:sqlite"],"type":"sql_injection","year":"2008"},"n_packages":0,"n_references":6,"next":{"headline":"SQL injection in n/a","id":"CVE-2008-6594"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2008-6592"},"products":["n/a"],"published":"2009-04-03","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2010-3484","kev_date_added":null,"published":"2010-09-22"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2010-3485","kev_date_added":null,"published":"2010-09-22"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2008-6592","kev_date_added":null,"published":"2009-04-03"},{"cvss_score":6.8,"headline":"SQL injection in n/a","id":"CVE-2010-4752","kev_date_added":null,"published":"2011-03-01"},{"cvss_score":6,"headline":"SQL injection in n/a","id":"CVE-2010-4751","kev_date_added":null,"published":"2011-03-01"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2008-6590","kev_date_added":null,"published":"2009-04-03"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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 inject arbitrary PHP code via SQL injection in the dlid parameter, leading to code execution and data modification.","url":"https://insights.sbomify.com/CVE-2008-6593/"}