Wails: wildcardPatternToRegex allows Origin bypass via suffix match in BindingsAllowedOrigins
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in github.com/wailsapp/wails/v2 2.13.0.
Wails is a framework for building desktop applications using Go and web technologies. From 2.0.0 until 2.13.0, BindingsAllowedOrigins in v2/internal/frontend/originvalidator/originValidator.go passes wildcard patterns to wildcardPatternToRegex, which expands every asterisk to an unrestricted regular-expression match. When an application configures a trailing or partial-label wildcard immediately after an allowed domain, an attacker-controlled lookalike origin can match the allowed suffix and invoke bound Go methods through IPC. A complete-component subdomain wildcard is an unaffected configuration. The resulting confidentiality, integrity, and availability impact depends on the file, database, command, credential, or other operations exposed by the application's bound methods. This issue is fixed in version 2.13.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| wailsapp | >=2.0.0 <2.13.0 | ||
| go: github.com/wailsapp/wails/v2 | >=2.0.0 <2.13.0 | 2.13.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket