Static-asset interruption via cached error responses
Published Aug 1, 2022 · Updated Apr 23, 2025
Cache poisoning in Discourse before 2.8.7 and beta before 2.9.0.beta8 allows remote attackers to interrupt static-asset delivery. The default NGINX static-asset location cached every upstream status for one minute, making an attacker-triggered error the cached response for later requests to that asset. No authentication or user interaction is required; the bounded consequence is temporary failure to deliver targeted static assets through installations using that default proxy rule.
Summary
What happened
Cache poisoning in Discourse before 2.8.7 and beta before 2.9.0.beta8 allows remote attackers to interrupt static-asset delivery. The default NGINX static-asset location cached every upstream status for one minute, making an attacker-triggered error the cached response for later requests to that asset. No authentication or user interaction is required; the bounded consequence is temporary failure to deliver targeted static assets through installations using that default proxy rule.
The record
- CVE
- CVE-2022-31182
- Published
- Aug 1, 2022
- Updated
- Apr 23, 2025
- Vendor
- Discourse
- Product
- Discourse
- Classifications
- CWE-404, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 2.8.7
- Affected versionversion=< 2.9.0.beta8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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