Skip to content

Attacker can prevent users from accessing received emails

High
charlag published GHSA-5h47-g927-629g Jan 25, 2024

Package

No package listed

Affected versions

>=3.118.12, < 3.119.10

Patched versions

3.119.10

Description

Summary

An attacker is able to send a manipulated email so that the user can no longer use the app to get access to received emails.

Details

By sending a manipulated email, an attacker could put the app into an unusable state. In this case, a user can no longer access received e-mails. Since the vulnerability affects not only the app, but also the web application, a user in this case has no way to access received emails.

PoC

  1. The attacker sends an email to another Tutanota user via a Tutanota account. To encrypt, however, it does not use the recipient's public key, but another. This could e.g. done via Burp by intercepting the response from the server and replace the public key of recipient with another.
  2. The victim receives the e-mail and sees the occurrence of an error message (similar to Figure 1). After receiving the manipulated e-mail, it is temporarily unable to display new mails in some cases. It is also not possible to move emails. Some settings cannot be changed in this case. Example is the audit log no longer updated, in which important actions such as disabling two-factor authentication are displayed.
  3. Because of this behavior, a user would probably log in to the app again.
  4. After a re-login, no e-mails can be displayed in the inbox. The following figure shows that an error is displayed after re-login (Figure 1) and no e-mails can be displayed or read (Figure 2) in the inbox. This vulnerability affects not only the app, but also the web application, so a user will no longer have the ability to access received emails in the inbox.

Error message, in inbox
no mails available in inbox

Impact

Users cannot access and read received mails. Probably all clients are affected. Tested with iOS and web app.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

CVE-2024-23655

Weaknesses

No CWEs

Credits