How to fix: SQL error message in response
The response contains an SQL error message, indicating unhandled database exceptions are being returned to clients.
Why it matters
SQL error messages reveal the database type, query structure, table names, and column names, giving an attacker direct feedback for SQL injection probing. This dramatically reduces the effort needed for a successful injection attack.
When an SQL query fails and the exception is not caught, many frameworks return the raw error message to the HTTP response. This is the most direct form of SQL injection facilitation.
How to fix it
- 1Wrap all database calls in try/catch blocks
- 2Return only generic error messages to clients (status 500)
- 3Log the full SQL error to a server-side logging system with a correlation ID
- 4Set your framework to production mode to disable detailed error output
Code examples
Safe error handling
try {
const rows = await db.query(sql, params);
return Response.json(rows);
} catch (err) {
console.error("[DB Error]", err); // server-side only
return Response.json({ error: "Database error" }, { status: 500 });
}References
Detected automatically by VulnRadar. The check id is sql-error-exposure, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is SQL error message in response?
- VulnRadar rates this high severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id sql-error-exposure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does SQL error message in response map to?
- It maps to CWE-209. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.