Log injection detected.

• Rule ID: java_lang_log_injection
• Languages: java
• Source: log_injection.yml

Description

Writing invalidated user input to log files can allow an attacker to forge log entries or inject malicious content into the logs. This rule looks for instances of user input sent to loggers.

Remediations

❌ Avoid using unsanitized user input in logger messages:

 String username = request.getParameter("username");
 log.warn("Username is" + username);

✅ If you need to identify a user, use their unique identifier instead of their personal identifiable information:

 String username = sanitized(request.getParameter("username"));
 log.warn("Username is" + username);

Resources

• [OWASP Log Injection] (https://owasp.org/www-community/attacks/Log_Injection)
• OWASP logging cheat sheet

Associated CWE

• CWE-117: Improper Output Neutralization for Logs

OWASP Top 10

• A09:2021 - Security Logging and Monitoring Failures

Configuration

To skip this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --skip-rule=java_lang_log_injection

To run only this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --only-rule=java_lang_log_injection