TL;DR: Authenticated SQL injection in MISP’s event index path can let a logged-in user abuse ORDER BY handling for boolean-blind and time-based extraction, according to Safe Security. Threat intel workflows need tighter query construction and database rights when structural input can reshape a query.
Editorial analysis by NHI Mgmt Group, based on content published by Safe Security: “Threat Research”.
Key questions
Q: Why does SQL injection still matter when authentication is already in place?
A: Authentication does not protect an application that can be tricked into issuing malicious SQL on behalf of a logged-in user or service account.
Q: How can security teams detect SQL injection?
A: Security teams detect SQL injection by monitoring application and database logs for malformed queries, repeated syntax errors, unexpected query patterns and parameter abuse.
Q: What fails when an authenticated search parameter can alter SQL structure?
A: The failure is a trust boundary collapse between application authentication and database authorisation.
Practitioner guidance
- Lock down SQL clause construction Remove user influence from ORDER BY and similar structural SQL elements, then review every endpoint that dynamically builds queries from request parameters.
- Reduce backend database privileges Run the MISP application with the minimum database rights needed for its actual query set, so an injection path cannot expose broader tables or administrative data.
- Add latency and repetition monitoring Alert on repeated parameter variation, unusual response timing, and probing of sensitive search endpoints that could indicate boolean-blind or time-based extraction.
Bottom line: The core issue is not just SQL injection, but the collapse of a query trust boundary inside an authenticated threat intelligence workflow.
Glossary terms: Unauthenticated SQL Injection, Boolean-Blind Oracle, Time-Based Oracle, Query Parameterization
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Authenticated access is not a substitute for query trust. This case shows how application-layer authentication can coexist with a broken authorisation boundary inside the database layer. When the query itself becomes attacker-influenced, the control failure is not just SQL injection but an assumption that logged-in users should be trusted to shape query structure. Practitioners should treat authenticated injection paths as governance failures across both application security and data access control.
A question worth separating out:
Q: Should organisations prioritise query parameterisation or database privilege reduction first?
A: They should do both, but privilege reduction is the faster containment step when a vulnerable query path already exists. Parameterisation removes the injection mechanism, while least-privilege database rights limit blast radius if a flaw remains. For platforms handling sensitive intelligence or operational data, leaving either control incomplete preserves avoidable exposure.
👉 Read our full editorial: Authenticated SQL injection in MISP exposes threat intel data