API access via overbroad CORS origin allowlist
Published Sep 30, 2021 · Updated Aug 4, 2024
CORS misconfiguration in nginz in Wire Server before 2.106.0 allows remote attackers to access the Wire API with a user's cookie. nginz returns Access-Control-Allow-Origin for every wire.com subdomain instead of limiting credentialed origins to applications that require the cookie. Exploitation requires script execution on an allowed subdomain and a victim with an active Wire session, exposing API data and actions available to that session.
Summary
What happened
CORS misconfiguration in nginz in Wire Server before 2.106.0 allows remote attackers to access the Wire API with a user's cookie. nginz returns Access-Control-Allow-Origin for every wire.com subdomain instead of limiting credentialed origins to applications that require the cookie. Exploitation requires script execution on an allowed subdomain and a victim with an active Wire session, exposing API data and actions available to that session.
The record
- CVE
- CVE-2021-41101
- Published
- Sep 30, 2021
- Updated
- Aug 4, 2024
- Vendor
- Wire Swiss GmbH
- Product
- Wire Server
- Classifications
- CWE-79, T1550.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 30, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.106.0
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