Skip to content

Latest commit

 

History

History
27 lines (18 loc) · 1.03 KB

File metadata and controls

27 lines (18 loc) · 1.03 KB
stage group info
Secure
Dynamic Analysis
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments

Improper Neutralization of CRLF Sequences in HTTP Headers

Description

By inserting Carriage Return / Line Feed (CRLF) characters, malicious users could potentially inject arbitrary data into HTTP responses. By modifying HTTP responses, attackers could conduct cross-site scripting or cache poisoning attacks against other users of the system.

Remediation

User input should never be used in constructing HTTP header responses without some form of validation against newlines. This includes URLs supplied by the user for HTTP redirects.

Details

ID Aggregated CWE Type Risk
113.1 false 113 Active high

Links