State changes via CSRF-exposed GET routes
Published Feb 8, 2022 · Updated Aug 4, 2024
Cross-site request forgery in Gitea before 1.11.2 allows remote attackers to trigger state-changing actions through crafted GET requests. Multiple user, organization, repository, admin-dashboard, and logout routes accepted GET for actions, while Gitea's CSRF handler checked only POST requests. A signed-in user's browser must request an attacker-controlled URL; the resulting action runs with that user's existing permissions.
Summary
What happened
Cross-site request forgery in Gitea before 1.11.2 allows remote attackers to trigger state-changing actions through crafted GET requests. Multiple user, organization, repository, admin-dashboard, and logout routes accepted GET for actions, while Gitea's CSRF handler checked only POST requests. A signed-in user's browser must request an attacker-controlled URL; the resulting action runs with that user's existing permissions.
The record
- CVE
- CVE-2021-45327
- Published
- Feb 8, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-294, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2022CVE 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.
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