Technical impact
Guard‑Core, an API security framework, neglects to validate the value extracted from the X‑Forwarded‑For header. The unchecked string is incorporated into Redis key names and glob patterns, creating an avenue for an attacker to influence how the system records and evaluates client activity. This unchecked input can cause the application to count unrelated client requests, trigger bans for legitimate users, or force the server to scan an ever‑growing set of Redis keys. The flaw reflects CWE‑20, which concerns improper input validation and could degrade confidentiality, integrity, and availability of the protected services.
Affected Systems
Products affected include the rennf93 Guard‑Core library, from its initial release 1.0.0 through all versions prior to 3.13.0. The issue was addressed in the 3.13.0 release, which implements validation of the X‑Forwarded‑For value before it is used in Redis key construction.
Risk and Exploitability
The CVSS score of 5.4 indicates a medium severity risk. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The most likely attack vector is a remote HTTP request that supplies a malicious X‑Forwarded‑For header in environments where the application trusts that header. An attacker controlling this header can cause the system to misinterpret activity, potentially leading to denial of service or incorrect request throttling. The lack of a publicly disclosed exploit and the need for a specific configuration reduce the current exploitability to moderate.