Back to list

Information Disclosure via X-LiteSpeed-Cache Header

Description

The 'X-LiteSpeed-Cache' header indicates that the application uses LiteSpeed Web Server’s caching mechanism. By revealing this header, attackers may identify the specific caching solution in use and tailor their exploits to known LiteSpeed vulnerabilities or misconfigurations. Disclosing caching details can also help malicious actors understand how the server manages cached content and how to manipulate or invalidate caches. Ultimately, exposing this information can lead to cache poisoning, unauthorized access to cached data, or other cache-related attacks if further weaknesses exist in the environment.

Remediation

Remove or obscure the 'X-LiteSpeed-Cache' header to avoid publicly disclosing the caching platform. Configure LiteSpeed Web Server settings or relevant directives so that detailed cache headers are not included in external responses. Keep LiteSpeed and any associated plugins or modules updated with the latest security patches to reduce risks related to known exploits. If you use reverse proxies or load balancers, ensure that they strip or rewrite headers revealing internal caching details. Additionally, employ a Web Application Firewall (WAF) or intrusion detection system to identify suspicious traffic patterns aimed at exploiting cache logic. Regularly review header settings to confirm no sensitive information is inadvertently leaked about your cache configuration.

References

https://www.litespeedtech.com/support/wiki/doku.phphttps://owasp.org/www-community/attacks/Cache_poisoning

Severity

MEDIUM

Owasp

Code: A05:2021

Category: Security Misconfiguration

Classification

CWE-200
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

5.4

CVSS:4.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

5.4