Ensure the LimitRequestLine directive is Set to 8190 or less but not 0 (Automated)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-apache24-10.1 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Apache24 10.1?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-apache24-10-1)More formats (shields.io, HTML) on the badges page.
---
name: cis-apache24-10.1
description: "Ensure the LimitRequestLine directive is Set to 8190 or less but not 0 (Automated)"
category: cis-apache
version: "2.3.0"
author: cyberstrike-official
tags: [cis, apache, linux, request-limits, buffer-overflow, limit-request-line]
cis_id: "10.1"
cis_benchmark: "CIS Apache HTTP Server 2.4 Benchmark v2.3.0"
tech_stack: [linux, apache]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# Ensure the LimitRequestLine directive is Set to 8190 or less but not 0 (Automated)
## Profile Applicability
- Level 2
## Description
Buffer Overflow attacks attempt to exploit an application by providing more data than the application buffer can contain. If the application allows copying data to the buffer to overflow the boundaries of the buffer, then the application is vulnerable to a buffer overflow. The results of Buffer overflow vulnerabilities vary, and may result in the application crashing, or may allow the attacker to execute instructions provided in the data. The Apache `LimitRequest*` directives allow the Apache web server to limit the sizes of requests and request fields and can be used to help protect programs and applications processing those requests.
Specifically, the `LimitRequestLine` directive limits the allowed size of a client's HTTP request-line, which consists of the HTTP method, URI, and protocol version.
## Rationale
The limiting of the size of the request line is helpful so that the web server can prevent an unexpectedly long or large request from being passed to a potentially vulnerable CGI program, module or application that would have attempted to process the request. Of course, the underlying dependency is that we need to set the limits high enough to not interfere with any one application on the server, while setting them low enough to be of value in protecting the applications. Since the configuration directive is available only at the server configuration level, it is not possible to tune the value for different portions of the same web server. Please read the Apache documentation carefully, as these requests may interfere with the expected functionality of some web applications.
## Audit
Perform the following steps to determine if the recommended state is implemented:
Verify that the `LimitRequestLine` directive is in the Apache configuration and has a value of `8190` or less.
## Remediation
Perform the following to implement the recommended state:
Add or modify the `LimitRequestLine` directive in the Apache configuration to have a value of `8190` or shorter.
```apache
LimitRequestLine 8190
```
## Default Value
```apache
LimitRequestLine 8190
```
## References
1. https://httpd.apache.org/docs/2.4/mod/core.html#limitrequestline
## CIS Controls
**v8:**
- 4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure
- Establish and maintain a secure configuration process for network devices. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
**v7:**
- 5.1 Establish Secure Configurations
- Maintain documented, standard security configuration standards for all authorized operating systems and software.
## Profile
- Level 2
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!