XSS over SMS: Hacking Text Messages in Verizon Messages

Verizon Messages (Message+) is a group of software clients available for mobile, desktop, and web aimed at enhancing/unifying the VZW text messaging experience across multiple devices. While it has a few additional features outside of SMS, I was most interested in activating it for its web app client when at a desktop/laptop.

After I installed the Android app and signed up, I logged in to the web app and starting using it. After a while, I noticed that messages containing links were being displayed with a preview/summary embedded in both the web and mobile interfaces.

I was interested in learning more about the types of links that were supported (images, videos, etc.) and how they were parsed. It was easier to start with the web app, so I sent myself a few test links. Here’s how a few examples were rendered:

It seemed pretty straightforward: HTML web pages were parsed server side and returned the URL’s Open Graph properties. Here’s a partial response:

As you can see, the response contains the OG attributes used in the UI’s preview elements. Note the imageUrl is actually a proxied image returned by Verizon’s servers (rather than an external host) — this is generally a good move to maintain more control over the images rendered in the user’s browser.

Since the “attachment” preview attributes were fetched asynchronously (and the resulting markup rendered client side), I decided to check for DOM XSS vectors that may have been overlooked. I texted myself some more test links — this time with some special characters in order to see how the web app would render them. After sending some single quotes included in the querystring of a test URL, I immediately noticed I was able to break out of the HREF attribute in the main anchor element above. Here is an example payload:

And the resulting markup:

By forcing the anchor to cover the user’s entire screen with inline styles, the onmouseover event triggers immediately upon opening the message:

This meant that an attacker could control the page with a specifically crafted text message, resulting in a complete takeover of the user’s session — this would allow control of any functionality, including sending and receiving SMS messages on behalf of the victim.

With the PoC working, I started searching the JavaScript sources to track down the cause of the issue. I soon found where the main attachment anchor was prepared:

Note how the HREF value is surrounded by single quotes. While there would have been a few ways to resolve this specific issue, the best option would have been to use the DOM API, e.g.:

Update: Looks like they did end up using the DOM API — see below.


I sent the PoC and screenshots/video of the issue to Verizon. As always, they were quick to respond, appreciated the report, and patched the issue quickly.

2016-11-18 Sent initial report of vuln
2016-11-18 Received response, working on it immediately
2016-12-09 Confirmed a patched was released


Share this: Facebooktwittergoogle_pluslinkedin
  • Andrew Harrison

    But did they give you any $?

  • Well done! What was their response? Any thanks or other benefits? But it’s very nice that such a huge company takes your information serious and fixed the problem immediately.

    • Randy Westergren

      Absolutely. They definitely were appreciative and credited me six months on my wireless bill.