Comment spam bypass via trusted forwarding headers
Published Aug 19, 2024 · Updated Aug 20, 2024
Client IP spoofing in Typecho 1.3.0 allows remote attackers to bypass comment spam controls via forged forwarding headers. The Request::getIp method trusts the first X-Forwarded-For value, or Client-Ip fallback, without restricting those headers to trusted proxies. Unauthenticated access to an enabled comment form is sufficient to evade per-IP throttling and flood a post with comments.
Summary
What happened
Client IP spoofing in Typecho 1.3.0 allows remote attackers to bypass comment spam controls via forged forwarding headers. The Request::getIp method trusts the first X-Forwarded-For value, or Client-Ip fallback, without restricting those headers to trusted proxies. Unauthenticated access to an enabled comment form is sufficient to evade per-IP throttling and flood a post with comments.
The record
- CVE
- CVE-2024-35538
- Published
- Aug 19, 2024
- Updated
- Aug 20, 2024
- Vendor
- Typecho
- Product
- Typecho
- Classifications
- CWE-290, CWE-444
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Typecho client-IP spoofing comment-spam exploitfunctional · 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