Skip to main content

Wire CVE-2021-41100

CRITICAL
Improper Authorization (CWE-285)
2021-10-04 security-advisories@github.com
9.8
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

1
CVE Published
Oct 04, 2021 - 19:15 nvd
CRITICAL 9.8

DescriptionNVD

Wire-server is the backing server for the open source wire secure messaging application. In affected versions it is possible to trigger email address change of a user with only the short-lived session token in the Authorization header. As the short-lived token is only meant as means of authentication by the client for less critical requests to the backend, the ability to change the email address with a short-lived token constitutes a privilege escalation attack. Since the attacker can change the password after setting the email address to one that they control, changing the email address can result in an account takeover by the attacker. Short-lived tokens can be requested from the backend by Wire clients using the long lived tokens, after which the long lived tokens can be stored securely, for example on the devices key chain. The short lived tokens can then be used to authenticate the client towards the backend for frequently performed actions such as sending and receiving messages. While short-lived tokens should not be available to an attacker per-se, they are used more often and in the shape of an HTTP header, increasing the risk of exposure to an attacker relative to the long-lived tokens, which are stored and transmitted in cookies. If you are running an on-prem instance and provision all users with SCIM, you are not affected by this issue (changing email is blocked for SCIM users). SAML single-sign-on is unaffected by this issue, and behaves identically before and after this update. The reason is that the email address used as SAML NameID is stored in a different location in the databse from the one used to contact the user outside wire. Version 2021-08-16 and later provide a new end-point that requires both the long-lived client cookie and Authorization header. The old end-point has been removed. If you are running an on-prem instance with at least some of the users invited or provisioned via SAML SSO and you cannot update then you can block /self/email on nginz (or in any other proxies or firewalls you may have set up). You don't need to discriminate by verb: /self/email only accepts PUT and DELETE, and DELETE is almost never used.

AnalysisAI

Wire-server is the backing server for the open source wire secure messaging application. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-285. Wire-server is the backing server for the open source wire secure messaging application. In affected versions it is possible to trigger email address change of a user with only the short-lived session token in the Authorization header. As the short-lived token is only meant as means of authentication by the client for less critical requests to the backend, the ability to change the email address with a short-lived token constitutes a privilege escalation attack. Since the attacker can change the password after setting the email address to one that they control, changing the email address can result in an account takeover by the attacker. Short-lived tokens can be requested from the backend by Wire clients using the long lived tokens, after which the long lived tokens can be stored securely, for example on the devices key chain. The short lived tokens can then be used to authenticate the client towards the backend for frequently performed actions such as sending and receiving messages. While short-lived tokens should not be available to an attacker per-se, they are used more often and in the shape of an HTTP header, increasing the risk of exposure to an attacker relative to the long-lived tokens, which are stored and transmitted in cookies. If you are running an on-prem instance and provision all users with SCIM, you are not affected by this issue (changing email is blocked for SCIM users). SAML single-sign-on is unaffected by this issue, and behaves identically before and after this update. The reason is that the email address used as SAML NameID is stored in a different location in the databse from the one used to contact the user outside wire. Version 2021-08-16 and later provide a new end-point that requires both the long-lived client cookie and Authorization header. The old end-point has been removed. If you are running an on-prem instance with at least some of the users invited or provisioned via SAML SSO and you cannot update then you can block /self/email on nginz (or in any other proxies or firewalls you may have set up). You don't need to discriminate by verb: /self/email only accepts PUT and DELETE, and DELETE is almost never used. Affected products include: Wire Wire-Server. Version information: Version 2021.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.

More in Wire

View all
CVE-2020-27853 CRITICAL POC
9.8 Oct 27

Wire before 2020-10-16 allows remote attackers to cause a denial of service (application crash) or possibly execute arbi

CVE-2021-21382 CRITICAL POC
9.6 Jun 11

Restund is an open source NAT traversal server. Rated critical severity (CVSS 9.6), this vulnerability is remotely explo

CVE-2021-29508 CRITICAL POC
9.1 May 11

Due to how Wire handles type information in its serialization format, malicious payloads can be passed to a deserializer

CVE-2020-15258 HIGH POC
8.0 Oct 16

In Wire before 3.20.x, `shell.openExternal` was used without checking the URL. Rated high severity (CVSS 8.0), this vuln

CVE-2018-8909 HIGH POC
7.5 Mar 22

The Wire application before 2018-03-07 for Android allows attackers to write to pathnames outside of the downloads direc

CVE-2021-32683 MEDIUM POC
6.1 Jun 15

wire-webapp is the web version of Wire, an open-source messenger. Rated medium severity (CVSS 6.1), this vulnerability i

CVE-2021-41093 CRITICAL
9.8 Oct 04

Wire is an open source secure messenger. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,

CVE-2023-48221 HIGH
8.8 Nov 20

wire-avs provides Audio, Visual, and Signaling (AVS) functionality sure the secure messaging software Wire. Rated high s

CVE-2022-43673 MEDIUM POC
4.7 Nov 18

Wire through 3.22.3993 on Windows advertises deletion of sent messages; nonetheless, all messages can be retrieved (for

CVE-2022-31122 HIGH
8.1 Oct 18

Wire is an encrypted communication and collaboration platform. Rated high severity (CVSS 8.1), this vulnerability is rem

CVE-2022-23610 HIGH
8.1 Mar 16

wire-server provides back end services for Wire, an open source messenger. Rated high severity (CVSS 8.1), this vulnerab

CVE-2023-22737 MEDIUM
6.5 Jan 28

wire-server provides back end services for Wire, a team communication and collaboration platform. Rated medium severity

Share

CVE-2021-41100 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy