Live data from Hacker News

A clickjacking vulnerability in WhatsApp that enables phishing attacks

00xbyte.github.io

31–40 of 84 posts

Re: A clickjacking vulnerability in WhatsApp that enables phishing attacks

#31
post #22
post #6

It's disappointing that Meta chose not to fix this and chose not to reward this researcher with a bug bounty.

I reported a similar issue to Google early this year and they declined the submission because it "can only result from social engineering" and "we think that addressing it would not make our users significantly less vulnerable". I won't mention the details here but Google Search sometimes rewrite URLs in such way that an attacker can spoof the actual URL. My advice is to never trust URLs displayed by websites and app…

> I won't mention the details here but Google Search sometimes rewrite URLs in such way that an attacker can spoof the actual URL.

I think I saw something like this a while ago, with some fake KeePass website maybe.

Re: A clickjacking vulnerability in WhatsApp that enables phishing attacks

#33
post #14

Earlier quoted context omitted.

The article says "I decided to intercept a message via WA web".

That was the initial idea, but it failed because Whatsapp traffic is end to end encrytped. The second idea, which actually worked, was to put a breakpoint in Whatsapp while running in an emulator.

No, not an emulator. Just using your browser's JavaScript debugger.

You can do that on any website.

Re: A clickjacking vulnerability in WhatsApp that enables phishing attacks

#34
post #16

Earlier quoted context omitted.

I expect they probably didn't make clear exactly what they wanted fixed (blacklisting the RTL character) and Meta thought they wanted all misleading URLs fixed which is not really possible.

That’s still a Meta problem. Simply confirming the PoC should have made it clear that they need to fix something.

POC?

Re: A clickjacking vulnerability in WhatsApp that enables phishing attacks

#38
Everyone fixing on the UTF RTL character but Meta should have at least acknowledged the issue with the preview URL that can be different from the message URL. I understand that this is probably to unfurl shortened URLs, but there has to be some clever workaround that Meta & Whatsapp can implement

Re: A clickjacking vulnerability in WhatsApp that enables phishing attacks

#40

Preview and message are sent separately. My intuition tells me the preview is used to track user activity. I wish I could contact the author to know more about how WhatsApp tracks activity

They cache the preview for subsequent messages containing the same link. For example, if a link is making the rounds and gets sent 200k times in an hour, they don't call the URL 200k times to build the preview, as that's a huge waste of resources on both sides, with a huge chance that the servers containing the link gets DDOSed
Post reply on HN