Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
The product receives data from an HTTP agent/component, and it places this data in HTTP response headers without neutralizing CRLF sequences.
An attacker can inject CRLF sequences into HTTP headers to create additional headers or response body content. This can lead to cache poisoning, cross-site scripting, or other attacks.
Como corrigir esta vulnerabilidade
Estratégias de prevenção para HTTP Response Splitting baseadas em 3 regras de detecção do Shoulder.
Strip CRLF characters from user input before setting HTTP headers
package main - import "net/http" - - func handler(w http.ResponseWriter, r *http.Request) { - lang := r.URL.Query().Get("lang") - // Vulnerable: user input set as header value - w.Header().Set("Content-Language", lang) + import ( + "net/http" + "strings" + ) + + func sanitizeHeaderValue(s string) string { + s = strings.ReplaceAll(s, "\r", "") + s = strings.ReplaceAll(s, "\n", "") + return s + } + + func handler(w http.ResponseWriter, r *http.Request) { + lang := r.URL.Query().Get("lang") + // Safe: CRLF characters stripped + w.Header().Set("Content-Language", sanitizeHeaderValue(lang)) w.Write([]byte("OK")) }
Strip CRLF characters from user input before using in HTTP headers
- from flask import request, make_response - - @app.route('/download') - def download(): - filename = request.args.get('filename') - response = make_response("content") - response.headers['Content-Disposition'] = f'attachment; filename="{filename}"' + import re + from flask import request, make_response + + def sanitize_header(value): + return re.sub(r'[\r\n]', '', str(value)) + + @app.route('/download') + def download(): + filename = request.args.get('filename', '') + safe_filename = sanitize_header(filename) + response = make_response("content") + response.headers['Content-Disposition'] = f'attachment; filename="{safe_filename}"' return response
Encontre vulnerabilidades no seu código
Use o Shoulder para escanear seu código em busca de padrões Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting'). 3 regras.
# Scan with Shoulder CLI npx @shoulderdev/cli trust --cwe=113 # Or scan entire project npx @shoulderdev/cli trust .
Regras de Detecção (3)
O que observar nas revisões de código
Estes padrões indicam vulnerabilidades potenciais de Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting'). Procure-os durante revisões de código e auditorias de segurança.
Escaneie seu código para Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
O Shoulder CLI encontra padrões vulneráveis em todo o seu código.