{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-1100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-1100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1100 is a critical SQL injection vulnerability in Vadi Corporate Information Systems DIGIKENT GIS, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-1100 and fix it if it is affected.\n\nWhat it is: CVE-2024-1100 is a critical SQL injection vulnerability in Vadi Corporate Information Systems DIGIKENT GIS, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-1100 in the wild and no public exploit code.\n\nAffected product: Vadi Corporate Information Systems DIGIKENT GIS. 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-2024-1100/ (Markdown: https://insights.sbomify.com/CVE-2024-1100/index.md)","id":"CVE-2024-1100","markdown":"https://insights.sbomify.com/CVE-2024-1100/index.md","name":"CVE-2024-1100","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GIS software","requires_auth":"none","summary":"An attacker can execute arbitrary SQL commands in DIGIKENT GIS, potentially reading or modifying sensitive geographic and corporate data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TR-CERT","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Vadi Corporate Information Systems DIGIKENT GIS allows SQL Injection.\n\nThis issue affects DIGIKENT GIS: through 2.23.5.","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":"SQLi in Vadi Corporate Information Systems' DIGIKENT GIS","id":"CVE-2024-1100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Jberet: jberet-core logging database credentials","id":"CVE-2024-1102"},"packages":[],"prev":{"headline":"Rebuild read-raw getFileOfData cross site scripting","id":"CVE-2024-1099"},"products":["DIGIKENT GIS"],"published":"2024-05-30","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-03","vendors":["Vadi Corporate Information Systems"]},"summary":"An attacker can execute arbitrary SQL commands in DIGIKENT GIS, potentially reading or modifying sensitive geographic and corporate data.","url":"https://insights.sbomify.com/CVE-2024-1100/"}