Unauthenticated route parameter manipulation via wildcard normalization
Published Jul 5, 2022 · Updated Aug 3, 2024
Path traversal in Beego before 1.12.11 and 2.0.0 through 2.0.3 allows remote attackers to manipulate route parameters. The leafInfo.match function passes request-controlled wildcard segments containing dot-dot elements to path.Join, which normalizes them before setting captured parameters or testing a route regular expression. Exploitation requires an application route with wildcard or regular-expression matching, and the resulting impact depends on how the application uses the replaced parameter values.
Summary
What happened
Path traversal in Beego before 1.12.11 and 2.0.0 through 2.0.3 allows remote attackers to manipulate route parameters. The leafInfo.match function passes request-controlled wildcard segments containing dot-dot elements to path.Join, which normalizes them before setting captured parameters or testing a route regular expression. Exploitation requires an application route with wildcard or regular-expression matching, and the resulting impact depends on how the application uses the replaced parameter values.
The record
- CVE
- CVE-2022-31836
- Published
- Jul 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Weakness, pattern, technique
Public exploit references
- Upstream wildcard-route proof of conceptproof 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