Unauthenticated whitelist bypass via spoofed forwarding header
Published May 25, 2020 · Updated Aug 4, 2024
Authentication bypass in the Knock Knock plugin for Craft CMS before 1.2.8 allows remote attackers to access IP-whitelisted content. The IP whitelist trusts the attacker-controlled X-Forwarded-For header as the visitor address and compares it directly with allowed IPs. A request bearing an allowed address therefore passes the whitelist without the source host owning that address, exposing only content protected by this IP gate.
Summary
What happened
Authentication bypass in the Knock Knock plugin for Craft CMS before 1.2.8 allows remote attackers to access IP-whitelisted content. The IP whitelist trusts the attacker-controlled X-Forwarded-For header as the visitor address and compares it directly with allowed IPs. A request bearing an allowed address therefore passes the whitelist without the source host owning that address, exposing only content protected by this IP gate.
The record
- CVE
- CVE-2020-13485
- Published
- May 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-697, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- X-Forwarded-For whitelist-bypass requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo