meta_pixel
Tapesearch Logo
Log in
SANS Internet Stormcenter Daily Cyber Security Podcast (Stormcast)

ISC StormCast for Thursday, March 21st 2019

SANS Internet Stormcenter Daily Cyber Security Podcast (Stormcast)

SANS ISC Handlers

Tech News, News, Technology

4.9696 Ratings

🗓️ 21 March 2019

⏱️ 5 minutes

🧾️ Download transcript

Summary

Daily 5 min cyber security news summary. News, patches, vulnerabilities and trends in information and network security. Google Photo xsleaks; Fake CDC Emails; Atlassian Sourcetree Vulnerability; Microsoft Defender for MacOS

Transcript

Click on a timestamp to play from that location

0:00.0

Hello, welcome to the Friday, March 22nd, 2019 edition of the Sansonet Storm Center's Stormcast.

0:07.3

My name is Johannes Ulrich.

0:09.0

And today I'm recording from Riyadh, Saudi Arabia.

0:13.1

Well, and that's also the answer for this month's challenge.

0:17.7

We got a ton of submissions.

0:20.4

I think the best hint that I probably gave was a picture

0:26.0

that I posted on Twitter. We got a number of submissions based on that. Also, once I ever mentioned

0:32.0

the local time here that narrowed it down somewhat, but actually probably a couple hundred submissions and

0:39.3

only two guessed the city correctly. The winner who's the person that first submitted the right

0:45.9

answer should receive an email from me sometime later today. Well about talking about images and associated metadata. Imperva has an interesting blog about

1:00.0

vulnerability in Google Photos that allowed others to guess the location and time and other

1:08.3

parameters of photos that you have stored with Google Photos.

1:13.2

The problem here is the API that Google exposed in order to search for photos and a neat

1:21.9

sort of cross-site timing attack that Imperva was able to exploit in order to actually retrieve search results.

1:30.9

In order to exploit the vulnerability, the victim has to be logged into Google Photos and has to be

1:36.9

visiting a malicious website. So this sounds very much like cross-side request forging and

1:42.7

in essence it is cross-side request forging and in essence it is cross-side request

1:45.0

forging with an interesting twist to get around same origin policy. Due to same origin

1:52.0

policy, the attacker will not receive a response back from this web service, but depending

1:59.3

on whether or not the search returned any results

2:02.6

or not, the time required for the error message to come back to the attacker will be different.

2:09.6

So essentially the attacker will have to prude force things like location and time,

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from SANS ISC Handlers, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of SANS ISC Handlers and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2025.