CVE-2024-1100: SQLi in Vadi Corporate Information Systems' DIGIKENT GIS
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Vadi Corporate Information Systems DIGIKENT GIS allows SQL Injection.
This issue affects DIGIKENT GIS: through 2.23.5.
Security readout for executives and security teams
Plain-English summary
CVE-2024-1100 is a critical SQL injection vulnerability in Vadi Corporate Information Systems DIGIKENT GIS. The record says versions through 2.23.5 are affected. A remote attacker may be able to interfere with the backing database, creating risk to data confidentiality, integrity, and availability.
Executive priority
Treat this as urgent for any organization using DIGIKENT GIS. The vulnerability is critical, unauthenticated, and network-reachable according to the CVSS data, but active exploitation is not established by the provided sources.
Technical view
The CVE describes CWE-89 SQL injection caused by improper neutralization of SQL command elements. CVSS 4.0 rates it 10.0 with network attack vector, low complexity, no privileges, no user interaction, and high vulnerable-system and subsequent-system impacts.
Likely exposure
Exposure is likely limited to organizations running Vadi DIGIKENT GIS through version 2.23.5, especially if the application is reachable over a network. The bundle does not identify specific hosted deployments, modules, endpoints, or default exposure patterns.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is still severe because the CVSS vector indicates unauthenticated, network-reachable exploitation with high impact if a vulnerable instance is accessible.
Researcher notes
Evidence is concise and lacks endpoint, proof-of-concept, patch, or workaround details. The affected-version statement says through 2.23.5, while the structured affected entry is sparse. Validate directly against vendor or government advisories before making product-wide assumptions.
Mitigation direction
Identify all DIGIKENT GIS deployments and confirm exact versions.
Check Vadi and Turkish government guidance for fixed versions or vendor mitigations.
Restrict network access to DIGIKENT GIS where business operations allow.
Increase monitoring for database errors, unusual queries, and suspicious application requests.
Prioritize remediation for internet-facing or third-party-accessible instances.
Validation and detection
Confirm whether any instance runs DIGIKENT GIS through 2.23.5.
Review vendor and government advisories for current remediation status.
Check logs for anomalous request patterns and SQL error responses.
Verify database permissions follow least-privilege principles for the application account.
Document compensating controls for any system that cannot be updated promptly.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.