Quantcast
Channel: CodeSection,代码区,网络安全 - CodeSec
Viewing all articles
Browse latest Browse all 12749

Understanding Security by Country: SSL

0
0

With Shodan it's easy to get an overview of the security for a country. Real-world borders don't necessarily translate to the Internet but it can still reveal useful information as shown by OECD . I will show how I use Shodan to get a big picture view of a country; in this case I'm looking at the USA.

First, lets have a look at how SSL is deployed in the USA. I will start off by getting a breakdown of the SSL versions that are supported by web servers:

shodan stats --facets ssl.version country:US has_ssl:true HTTP

To do this I'm faceting on the ssl.version property which contains a list of SSL versions that the web server supports. This is possible because Shodan crawlers explicitly test for SSLv2 through TLSv1.2.


Understanding Security by Country: SSL

Unsurprisingly, the majority of the HTTPS servers are hosted by Akamai and Amazon. However, there's still a sizable chunk (600,000+) devices that support SSLv2 so lets look at those briefly:

shodan stats --facets org country:US ssl.version:sslv2 HTTP

Here I'm faceting on the org (organization) property and filtering for web servers that support SSLv2. This doesn't mean that they only accept SSLv2 connections but it is one of the versions the service supports.


Understanding Security by Country: SSL

Around25% of the services that support SSLv2 are operating on CenturyLink's network. Just looking at the results it seems like some of CenturyLink's modems are the reason for their #1 spot on the list. Their numbers are significantly higher than the next provider but I'm hoping these numbers will decline as CenturyLink phases out their older equipment.

The Shodan crawls also check for the various SSL vulnerabilities such as Heartbleed and FREAK so lets see how the US fares for those. For Heartbleed there are at least ~30,000 devices in the US still vulnerable to it.


Understanding Security by Country: SSL

Interestingly, Verizon Wireless is the network with the most services vulnerable to Heartbleed. The runner-up, Amazon, is less surprising since it's not unusual for people to deploy old images that haven't yet been patched (or lack protection). There are 2 types of devices operated by Verizon Wireless that are affected:

Wireless routers that run on the alternate HTTPS port 8443 and are made by CradlePoint Technology.

Digital billboards made by Watchfire Signs that run a web server on port 9443.

I have not heard of these products before but this explains why Verizon Wireless has the most devices affected by Heartbleed - I wouldn't have expected many regular web servers to operate on their network. The same analysis can be performed by looking at services that support export ciphers (CVE-2015-0204) which I will leave as an exercise.

Finally, lets look at the distribution of SSL certificates. It usually isn't a good sign if the same SSL certificate is deployed across a large number of devices. To see the usage of duplicate SSL certificates we can facet on the ssl.cert.fingerprint property:

shodan stats --facets ssl.cert.fingerprint country:us has_ssl:true http

The results of the command will give us the 10 most common SSL certificate fingerprints:


Understanding Security by Country: SSL

If you want to get more than 10 you can also provide a number to the facet. For example, this is how to get the top 100 SSL fingerprints:

shodan stats --facets ssl.cert.fingerprint:100 country:us has_ssl:true http

The most common SSL certificate is for what looks like Google's CDN on IPv6. However, the 2nd most often seen SSL certificate is for Ecommerce Corporation which is a familiar company if you've read some of myearlier articles on defaced websites. While we're looking at duplicate fingerprints, what about SSH fingerprints?

shodan stats --facets ssh.fingerprint country:us
Understanding Security by Country: SSL

The most common duplicate SSH fingerprint in the US belongs toGoDaddy. Looking at those results will require another blog post but the above is how I usually get started when trying to identify systemic problems.

Here is a short video that shows how I've done a similar analysis for Germany:

SSL is only one of many aspects that should be looked at and I will be discussing some other angles in future posts. I hope I've given you a better idea of how I use Shodan to breakdown SSL issues on a national level.


Viewing all articles
Browse latest Browse all 12749

Latest Images

Trending Articles





Latest Images