2016 · India · O - Public administration and defence · Data theft via SQL injection
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via SQL injection
Expertise to Execution
Evidence coverage: 4/6 stages, weight 22/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Leadership
(1) The Eastern India Regional Council of the Institute of Chartered Accountants of India runs public-facing membership web services holding member and registration records; the expectation for such a statutory professional body is that its public web application resist well-known attack classes and store member credentials securely. (2) Operationally, Kapustkiy enumerated several vulnerabilities on the website with ordinary web scanners and exploited an SQL-injection flaw with a commodity SQLi tool, pulling a database of about 17,000 records whose passwords were all stored in plain text, then leaked around 2,000; he first notified the site administrators by e-mail and got no answer, and the incident reached the public record only through his own leak - no acknowledgement or member notification from the council is documented. (3) The classification rests on the entry stage, where the vector is fully documented and load-bearing: the remedies for the exploited weakness (input validation, parameterised queries) and for the credential exposure (password hashing) sit squarely in the material column as standard, available technical knowledge, and the chain broke at execution because the council's day-to-day practice had never realised them - no source shows a strategic policy that existed unexecuted, nor a leadership decision that created the gap, so this is a knowing-doing gap within the material column (Expertise to Execution) rather than a Strategy-type reading. The ignored pre-publication warning and the absent victim disclosure are real response-stage conditions but are carried by one unanswered weekend e-mail and institutional silence (they would point to Expertise to Leadership), and detection rests on inference, so neither displaces the better-documented technical gaps; recovery was not in play (no disruption). RM29 (Expertise to Execution lens): secure-coding practice for injection flaws is standard developer knowledge, yet it never reached the production code of the council's own web application, so a commodity SQL-injection tool could reach the membership database (causal role: Enabling). RM26 (Expertise to Execution lens): the known remedy of hashing member passwords was never implemented - all passwords sat in plain text - so the theft handed out directly usable credentials instead of mere profile data (causal role: Amplifying). RM34 (Expertise to Execution lens): no monitoring or alert handling caught the intrusion or the dump; the only alert that existed was the external pentester's e-mail, and even that went unanswered (causal role: Obscuring). RM39 (Expertise to Execution lens): the council had no operational capacity to scope and communicate the incident - it issued no acknowledgement and no member notification, leaving the attacker's leak as the only account of what data had been exposed (causal role: Constraining).
RM29 — Secure-development / non-production exposureRM26 — Data-protection / cryptographic weaknessRM34 — Monitoring / detection / alert-handling gapRM39 — Breach notification / disclosure failureVictim identification: the dataset names the victim only as an Indian regional Council; DataBreaches.net identifies the Eastern Indian Regional Council as the Institute of Chartered Accountants of India's Eastern Regional Council (eirc-icai.org), not a university - press stories calling the records those of 17,000 students refer to the body's students/study-circle members. Sector follows the dataset's receiver category (state institutions / government ministries): the ICAI regional council is a statutory professional body exercising state-delegated regulatory functions. Whole-lifecycle evidence rests on attacker-side interviews (Softpedia, Security Affairs) and a leak-fields inspection by DataBreaches.net: the scale and the claim that the pentester notified the admins first are unverified attacker claims, and the council itself never commented; no CERT, regulator or court document about the incident was found, and no follow-up reporting on remediation was located. The absence of any victim acknowledgement or member notification rests on the silence of the available record, not on a source that states it. No related_rows in the case file. Link check: news.softpedia.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research.