You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a directory traversal issue in attachment downloads in Gmail. For non-gmail accounts, there is no path sanitization on the attachment filename in the email, so when attachments are downloaded, a file with any name and any contents can be written to anywhere on the filesystem that the Gmail app can access. This bug has the following limitations:
5
+
6
+
1) the email address has to be a non-Gmail and non Gmailified (Hotmail or Yahoo) account
7
+
2) the file can not overwrite an existing file, it has to be a file that doesn't already exist
8
+
3) there user has to click to download the attachment (and the path looks a bit weird on the screen)
9
+
10
+
It is possible to modify a EmailProviderBody database using this bug by placing a journal file in the databases directory.
11
+
12
+
Below is a PoC of an email that causes this issue. Attached is a python script that will send an email that causes this issue (don't forget to add in the to and from addresses, and your Gmail credentials). WARNING: this PoC will cause Gmail to crash repeatedly, and you will need to re-install it to get it to work again
13
+
14
+
Content-Type: multipart/mixed; boundary="---
15
+
-714A286D976BF3E58D9D671E37CBCF7C"
16
+
MIME-Version: 1.0
17
+
Subject: hello
18
+
To: <address>
19
+
From: natashenka@google.com
20
+
21
+
You will not see this in a MIME-aware mail reader.
22071,exploits/php/webapps/22071.txt,"WordPress Plugin FireStorm Professional Real Estate 2.06.01 - SQL Injection",2012-10-18,"Ashiyane Digital Security Team",webapps,php,
43158,exploits/hardware/webapps/43158.txt,"Icon Time Systems RTC-1000 Firmware 2.5.7458 - Cross-Site Scripting",2017-11-17,"Keith Thome",webapps,hardware,
0 commit comments