{"id":541,"date":"2018-04-27T15:55:32","date_gmt":"2018-04-27T22:55:32","guid":{"rendered":"https:\/\/eligrey.com\/blog\/?p=541"},"modified":"2018-11-21T01:56:43","modified_gmt":"2018-11-21T08:56:43","slug":"google-inbox-spoofing-vulnerability","status":"publish","type":"post","link":"https:\/\/eligrey.com\/blog\/google-inbox-spoofing-vulnerability\/","title":{"rendered":"Google Inbox spoofing vulnerability"},"content":{"rendered":"<p>On May 4th, 2017 I discovered and privately reported a recipient spoofing vulnerability in Google Inbox. I noticed that the composition box always hid the email addresses of named recipients without providing a way to inspect the actual email address, and figured out how to abuse this with mailto: links containing named recipients.<\/p>\n<p>The link <a href=\"https:\/\/go.eligrey.com\/security\/google-inbox-spoofing-vulnerability-exploit-direct.poc\">mailto:\u200b&#8221;support@paypal.com&#8221;\u200b&lt;scam@phisher.example&gt;<\/a> shows up as &#8220;support@paypal.com&#8221; in the Google Inbox composition window, visually identical to any email actually sent to PayPal. <\/p>\n<p>In order to exploit this vulnerability, the target user only needs to click on a malicious mailto: link. It can also be triggered by clicking on a direct link to Inbox&#8217;s mailto: handler page, as shown in <a href=\"https:\/\/go.eligrey.com\/security\/google-inbox-spoofing-vulnerability-exploit.poc\" target=\"_blank\" rel=\"nofollow noopener\">this example exploit link<\/a>.<\/p>\n<p>This vulnerability was still unfixed in all Google Inbox apps as of May 4th, 2018, a year after private disclosure.<\/p>\n<p><strong>Update<\/strong>: <a href=\"https:\/\/www.xda-developers.com\/google-fixes-flaw-spoof-inbox-by-gmail\/\">This vulnerability has been fixed in the Google Inbox webapp<\/a> as of May 18, 2018. The Android app still remains vulnerable.<\/p>\n<div id=\"attachment_549\" class=\"wp-caption aligncenter\" style=\"max-width: 575px; overflow: auto;\">\n<p><a href=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc.png\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-549 size-full\" src=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc.png\" sizes=\"auto, (max-width: 565px) 100vw, 565px\" srcset=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc.png 1130w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc-300x247.png 300w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc-768x633.png 768w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-poc-1024x844.png 1024w\" alt=\"\" width=\"565\" height=\"466\" \/><\/a><\/p>\n<p class=\"wp-caption-text\">The recipient \u201csupport@paypal.com\u201d being spoofed in the Google Inbox composition window. The actual recipient is \u201cscam@phisher.example\u201d.<\/p>\n<\/div>\n<p><!--more--><br \/>\nOn July 3rd, 2017 I noticed that Google had added hover tooltips to this field in Inbox, which made it possible for users to manually confirm the recipient email address. The default presentation of the email address was still vulnerable to spoofing, so I sent another email to Google.<\/p>\n<p><a href=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-546\" src=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update.png\" alt=\"\" width=\"706\" height=\"423\" srcset=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update.png 1412w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-300x180.png 300w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-768x460.png 768w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-1024x613.png 1024w\" sizes=\"auto, (max-width: 706px) 100vw, 706px\" \/><\/a><\/p>\n<p>I received no response for over 8 months, so I sent yet another email on March 16th, 2018.<\/p>\n<p><a href=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-547 size-full\" title=\"I decided to disclose this 1 week early \u00af\\_(\u30c4)_\/\u00af\" src=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2.png\" alt=\"\" width=\"706\" height=\"354\" srcset=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2.png 1412w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2-300x151.png 300w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2-768x386.png 768w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-2-1024x514.png 1024w\" sizes=\"auto, (max-width: 706px) 100vw, 706px\" \/><\/a><\/p>\n<p>Nine months after sending my emails I received this response, which doesn&#8217;t lead me to believe that Google is serious about fixing this vulnerability.<\/p>\n<p><a href=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-548\" src=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3.png\" alt=\"\" width=\"706\" height=\"245\" srcset=\"https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3.png 1412w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3-300x104.png 300w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3-768x267.png 768w, https:\/\/eligrey.com\/blog\/wp-content\/uploads\/2018\/04\/google-inbox-vulnerability-update-3-1024x355.png 1024w\" sizes=\"auto, (max-width: 706px) 100vw, 706px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>On May 4th, 2017 I discovered and privately reported a recipient spoofing vulnerability in Google Inbox. I noticed that the composition box always hid the email addresses of named recipients without providing a way to inspect the actual email address, and figured out how to abuse this with mailto: links containing named recipients. The link [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-541","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pfpUD-8J","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/posts\/541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/comments?post=541"}],"version-history":[{"count":0,"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/posts\/541\/revisions"}],"wp:attachment":[{"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/media?parent=541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/categories?post=541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eligrey.com\/blog\/wp-json\/wp\/v2\/tags?post=541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}