sc-header-injection

Detect and verify HTTP header CRLF injection vulnerabilities in web applications.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-header-injection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-header-injection
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-header-injection
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-header-injection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HTTP header injection and CRLF-related vulnerabilities occur when user-controlled input is unsafely placed into HTTP response headers, enabling header injection and response splitting.

Core Features & Use Cases

  • Detects CRLF injection in header handling across common web frameworks.
  • Validates and guides safe header usage to prevent response splitting and header pollution.
  • Provides practical verification steps for remediation and secure coding practices.

Quick Start

Run the scanner against your web app to detect and verify CRLF header injection vulnerabilities.

Frequently Asked Questions about sc-header-injection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect CRLF injection vulnerabilities in HTTP response headers?

To detect CRLF injection in HTTP response headers, scan your web application for instances where user-controlled input is unsafely placed into headers, enabling response splitting and header pollution. This Skill automates that detection process.

Does this CRLF header injection scanner work with Python, Node.js, and Java web apps?

Yes, this CRLF header injection scanner works with web services built with Python, Node.js, Java, Go, PHP, and associated middleware where response headers are influenced by user input.

What is HTTP header injection and how does response splitting occur?

HTTP header injection occurs when user-controlled input is unsafely placed into HTTP response headers. Attackers can insert CRLF sequences to split responses or pollute headers, enabling cross-site scripting and session fixation.

How do I verify and fix CRLF injection risks in my web framework?

To verify and fix CRLF injection risks, follow practical verification steps provided by the scanner. It guides safe header usage and secure coding practices to prevent response splitting across popular web frameworks.

What's the best way to prevent header pollution across multiple web frameworks?

The best way to prevent header pollution is to validate and guide safe header usage across common web frameworks. This Skill provides practical remediation steps and secure coding practices to ensure safe header handling.

Why does user input in HTTP headers cause CRLF vulnerabilities in my application?

User input causes CRLF vulnerabilities when unsafely placed into HTTP response headers without proper sanitization. This allows attackers to inject CRLF sequences, leading to response splitting and header injection attacks.