Aug 16 2023

TestSSL To Test TLS/SSL Encryption On Any Port

Category: Cryptograghy,Information Securitydisc7 @ 4:08 pm
Source: https://hackersonlineclub.com/testssl-testing-tls-ssl-encryption-port/

Testing TLS/SSL encryption anywhere on any port.

testssl.sh is a free command line tool, which checks a server’s service on any port for the support of TLS/SSL ciphers, protocols as well as some cryptography flaws on Linux servers, even it runs on macOS too.

It is also available in Kali Linux OS to test TLS/SSL encryption.

Key features

  • Clear output: you can tell easily whether anything is good or bad.
  • Machine readable output (CSV, two JSON formats)
  • No need to install or to configure something. No gems, CPAN, pip or the like.
  • Works out of the box: Linux, OSX/Darwin, FreeBSD, NetBSD, MSYS2/Cygwin, WSL (bash on Windows). Only OpenBSD needs bash.
  • A Dockerfile is provided, there’s also an official container build @ dockerhub.
  • Flexibility: You can test any SSL/TLS enabled and STARTTLS service, not only web servers at port 443.
  • Toolbox: Several command line options help you to run your test and configure your output.
  • Reliability: features are tested thoroughly.
  • Privacy: It’s only you who sees the result, not a third party.
  • Freedom: It’s 100% open source. You can look at the code, see what’s going on.
  • The development is open (GitHub) and participation is welcome.

License

This software is free. You can use it under the terms of GPLv2, see LICENSE.

Attribution is important for the future of this project — also in the internet. Thus if you’re offering a scanner based on testssl.sh as a public and/or paid service in the internet you are strongly encouraged to mention to your audience that you’re using this program and where to get this program from. That helps us to get bugfixes, other feedback and more contributions.

Compatibility

Testssl.sh is working on every Linux/BSD distribution out of the box. Latest by 2.9dev most of the limitations of disabled features from the openssl client are gone due to bash-socket-based checks.

As a result you can also use e.g. LibreSSL or OpenSSL >= 1.1.1 . testssl.sh also works on other unixoid systems out of the box, supposed they have /bin/bash >= version 3.2 and standard tools like sed and awk installed. An implicit (silent) check for binaries is done when you start testssl.sh . System V needs probably to have GNU grep installed. MacOS X and Windows (using MSYS2, Cygwin or WSL) work too.

Installation

You can download testssl.sh branch 3.2 just by cloning this git repository:

git clone –depth 1 https://github.com/drwetter/testssl.sh.git
3.2 is now the latest branch which evolved from 3.1dev. It’s in the release candidate phase. For the former stable version help yourself by downloading the ZIP or tar.gz archive. Just cd to the directory created (=INSTALLDIR) and run it off there.

Docker

Testssl.sh has minimal requirements. As stated you don’t have to install or build anything. You can just run it from the pulled/cloned directory. Still if you don’t want to pull the GitHub repo to your directory of choice you can pull a container from dockerhub and run it:

docker run –rm -ti drwetter/testssl.sh <your_cmd_line>

Or if you have cloned this repo you also can just cd to the INSTALLDIR and run

docker build . -t imagefoo && docker run –rm -t imagefoo example.com

For more please consult Dockerfile.md.

Status

Currently in the release candidate phase for version 3.2. Bigger features will be developed in a separate branch before merged into a 3.3dev to avoid hiccups or inconsistencies.

Version 3.0.X receives bugfixes, labeled as 3.0.1, 3.0.2 and so on. This will happen until 3.2 is released.

Support for 2.9.5 has been dropped. Supported is >= 3.0.x only.

Documentation

  1. See man page in groff, html and markdown format in ~/doc/.
  2. https://testssl.sh/ will help to get you started for TLS/SSL encryption testing.
  3. For the (older) version 2.8, Will Hunt provides a longer description, including useful background information.

Download TestSSL

Bulletproof TLS and PKI, Second Edition: Understanding and Deploying SSL/TLS and PKI to Secure Servers and Web Applications

CISSP training course

InfoSec tools | InfoSec services | InfoSec books | Follow our blog

Tags: PKI, SSL, TestSSL, TLS


Jan 21 2014

Why Two Thirds of Personal Banking Apps Have Vulnerabilities

Category: App Security,Mobile SecurityDISC @ 11:12 pm

Image representing iPhone as depicted in Crunc...

Image via CrunchBase

Personal Banking Apps study has been out,  a security researcher spent about 40 hours testing iPhone and iPad banking applications from the top 60 most influential banks in the world and his findings were totally shocking.

40 of those 60 applications were found to have major mobile security vulnerabilities, which is not something you’d expect to find in an application which authenticate you to your bank.

The conducted tests were split amongst six separate areas: transport security, compiler protection, UIWebViews, data storage, logs and binary analysis. Serious weaknesses were found in all of these areas.
40% of the applications can’t validate to the authenticity of SSL certificates, meaning that they’re vulnerable to monkey/man in the middle (MiTM) attacks

A full 90% of the apps contain non-SSL links, potentially allowing “an attacker to intercept the traffic and inject arbitrary JavaScript/HTML code in an attempt to create a fake login prompt or similar scam.”

50% “are vulnerable to JavaScript injections via insecure UIWebView implementations… allowing actions such as sending SMS or emails from the victim’s device.”

70% have no facility for any “alternative authentication solutions, such as multi-factor authentication, which could help to mitigate the risk of impersonation attacks.”

The incredibly troubling study brings to light a very serious problem for the banking industry — and for consumers, of course — that will only become more severe over time as mobile banking app usage grows. Sanchez notes in his report that the various security vulnerabilities he identified could allow malicious hackers to intercept sensitive data, install malware or even seize control of a victim’s device.

When Banks are using their mobile applications as a competitive advantage, you may think that they’d thoroughly test these applications for any existing security flaws with vulnerability assessment or mobile Penetration test, to reduce the vulnerabilities from two third to an acceptable level. Major security flaws shows that applications have not been tested for security vulnerabilities at every phase of the development. Above all it shows Banks have a weak Information Security Management System (ISMS) in place. This can be especially a worrisome trend for smaller Banks due to lack of existing information security resources and expertise.

Mobile Information Security and Privacy Books

Mobile Malware Protection from from phishing sites and malicious URLs




Tags: Banking Apps, Information Security Management System, SSL, Vulnerability (computing)