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

ISC StormCast for Monday, June 3rd 2019

SANS Internet Stormcenter Daily Cyber Security Podcast (Stormcast)

SANS ISC Handlers

Tech News, News

4.9754 Ratings

🗓️ 3 June 2019

⏱️ 6 minutes

🧾️ Download transcript

Summary

Daily 5 min cyber security news summary. News, patches, vulnerabilities and trends in information and network security. Google Outage; Siemens LOGO 8! BM Vulnerablity; Exposing tor users; nginx njs vulnerability; #google #siemens #nginx #tor

Transcript

Click on a timestamp to play from that location

0:00.0

Hello, welcome to the Monday, June 3rd, 2019 edition of the San Sanct Storm Center's Stormcast.

0:06.7

My name is Johannes Ulrich, and I'm quoting from San Antonio, Texas.

0:13.2

Google, today on Sunday, suffered a major outage across parts of its infrastructure.

0:19.8

Looks like it lasted about four hours. The result was

0:23.6

that Gmail and YouTube for example was not reachable, but the outage also affected a number of

0:31.6

third party services. Like for example, Snapchat and Discord were mentioned in news reports.

0:39.3

These services do rely on Google Cloud.

0:43.3

The outage appears to be somewhat focused in the eastern United States,

0:47.3

but these services were also not reachable for a number of users in California, for example.

0:56.3

So far Google hasn't released any details, but it promised to do so once they finished their

1:02.6

investigation.

1:05.5

And about a week ago, Siemens published a security announcement regarding its logo 8BM controllers.

1:14.6

These are logic controllers that you often find in automation environments, and these controllers

1:21.6

listen on port 10,0005. Turns out they're subject to an unauthenticated configuration override.

1:30.3

Also, an attacker could use this port to download configuration files from affected devices.

1:38.3

At this point, there is no patch available for this problem.

1:42.3

Siemens just recommends that you do not expose port

1:47.4

10,0005 of these devices to untrusted networks.

1:52.2

What it certainly sounds like a severe issue at this point, Shodan, for example, only lists

1:57.5

59 devices listening on this port. We also don't see a lot of scanning on

2:03.0

this port, so this is probably more an issue where an attacker would already have a foothold

2:08.3

in a network and then laterally move to exposed devices. And I've got an interesting blog post outlining a quick method how a malicious Tor exit node may potentially be able to obtain the real IP address of a host connecting through it.

...

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 2026.