Hibernate TRACE parameter logging writes SQL values to logs
Rule ID: vetkit.spring.jpa.sql-parameter-logging
Hibernate bound-parameter logging is set to TRACE (org.hibernate.orm.jdbc.bind / org.hibernate.type.descriptor.sql). Every query parameter, including passwords, tokens and personal data, is written to the application log.
Last updated:
Suite: Security
regex
Hibernate bound-parameter logging is set to TRACE (org.hibernate.orm.jdbc.bind / org.hibernate.type.descriptor.sql). Every query parameter, including passwords, tokens and personal data, is written to the application log.
Category: SECURITY · Engine rule severity: WARNING
How to fix it
Keep parameter tracing in a development profile only; production logs should not contain query values.
References
Source: packages/engine/rules/sast/config.yml.
Related checks
- Spring Boot spring.jpa.show-sql=true outside a dev profile
- Spring Boot YAML jpa show-sql: true outside a dev profile
- Spring YAML Hibernate TRACE parameter logging leaks SQL values
- Spring Boot actuator env show-values=always exposes secrets
- Spring Boot YAML show-values: always unmasks actuator env
- Spring Boot actuator exposure.include=* exposes all endpoints
Check your own repository for this
vetkit runs this rule as part of a repository audit, alongside secret scanning, dependency vulnerabilities, code quality and AI code risk checks. It reads a temporary checkout and never executes your code.
Start with the free Security Quick Scan · See how the platform works
Generated from shipped rule definitions at build time. Matching is a review signal, not proof of exploitability. “generic” denotes text matching, not complete language or framework coverage. Runtime configuration and available tools affect whether a rule runs.