> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/2-java/possible-clrf-injection-detected.md).

# Possible CLRF injection detected

## Overview

* **Rule ID**: `java_lang_crlf_injection`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-93

## Description

CRLF (Carriage Return Line Feed) injection vulnerability occurs when an attacker can insert line termination characters into a log message. This can result in forged log entries, compromising the integrity of log files.

## Remediation Guidelines

* Before logging user input data, it is essential to *strip any carriage return and line feed characters*. This practice prevents attackers from injecting malicious CRLF sequences into the log entries.

  ```java
  logger.info(userInput.replaceAll("[\r\n]+", ""));
  ```

## References

* [**OWASP CRLF Injection**](https://owasp.org/www-community/vulnerabilities/CRLF_Injection)
* [**OWASP Logging Cheat Sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)
* [**CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')**](https://cwe.mitre.org/data/definitions/93.html)
* [**OWASP Top 10: A03:2021 - Injection**](https://owasp.org/Top10/A03_2021-Injection/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)