Insufficient Transport Layer Security

Insufficient Transport Layer Security | Report Data

Analysis:

During the analysis, it was observed that the mentioned application was deployed over an unencrypted protocol (i.e. HTTP). Due to this user credentials are transmitted in plain text over the network. Please refer to the below-provided evidence.

Impact:

When the transport layer is not encrypted, all communication between the website and the server is sent in clear text which leaves it open to interception, injection, and redirection (also known as a man-in-the-middle/MITM attack).

An attacker may passively intercept the communication, giving them access to any sensitive data that is being transmitted such as usernames and passwords. An attacker may also actively inject/remove content from the communication, allowing the attacker to forge and omit information, inject malicious scripting, or cause the client to access remote untrusted content.

An attacker may also redirect the communication in such a way that the website and client are no longer communicating with each other, but instead are unknowingly communicating with the attacker in the context of the other trusted party.

Recommendation:

Recommendation to Enforce TLS:

Applications should be deployed over encrypted communication channels i.e. HTTPS.
At a minimum, do all the following:
Require HTTPS for all sensitive pages. Non-SSL requests to these pages should be redirected to the HTTPS page.
Ensure your certificate is valid, not expired, not revoked, and matches all domains used by the site.
The back-end and external connections made by the application should also use HTTPS or other encryption technologies.

Note: After deploying over the HTTPS, Set the ‘secure’ flag on all sensitive cookies.

References:

How to Enforce SSL/TLS – OWASP:

https://www.owasp.org/index.php/Top_10_2010-A9-Insufficient_Transport_Layer_Protection

ITLS – WebAppSec:

http://projects.webappsec.org/w/page/13246945/Insufficient%20Transport%20Layer%20Protection

Comments

Free Cybersecurity Certifications

Introduction to Cybersecurity Cybersecurity Essentials Networking Essentials Android Bug Bounty Hunting: Hunt Like a Rat Ethical Hacking Essentials (EHE) Digital Forensics Essentials (DFE) Network Defense Essentials (NDE) Introduction to Dark Web, Anonymity, and Cryptocurrency AWS Skill Builder Introduction to Cybersecurity Building a Cybersecurity Toolkit Cyber Aces Free Cyber Security Training Course Introduction to Information Security Penetration Testing - Discovering Vulnerabilities

Is your webcam exposed on the internet and everyone enjoying your personal moments? | How to check webcam or security camera is exposed on the internet or not?

Nowadays we start using many technology devices in our homes. Many people are installing CCTV or security cameras in their houses, private rooms, offices, private places, etc for security purposes and monitoring, but many of them don't know how to configure that device securely. So let's talk about CCTV and security cameras only. What do most CCTV/Security camera users believe? Most users believe that using a strong username and password on a camera administrative page protects them. (Partially true in the case of online cameras) Example: Why it is partially true? It's partially true because you are protecting only the camera administrative page which is also an important part. Still, you are not protecting the protocol used to control streaming media servers (Real-Time Streaming Protocol ( RTSP )). I have seen many online webcams whose administrative page is secured by strong credentials, but they forget to secure the RTSP protocol which gives me access to the streaming

Web Application Security Testing (WAPT) Interview Questions

Let's Contribute All Together For Creating a Questions Dump What are the vulnerabilities you have to test in the Login form, Payment gateway? What is clickjacking? What is the mitigation of clickjacking? What is CSRF? How to mitigate CSRF? Let's take an example, If a developer implements a CSRF token in a cookie, will it mitigate the CSRF issue? Is it possible to mitigate the CSRF by header? If yes why, if No why? If the data is in JSON format, how you will check the CSRF issue and what are the ways of exploitation? Where to implement the CSRF token and why? If the client doesn't want to change the UI or doesn't want to implement the CSRF tokens, and headers then what mitigation you recommended to the client for CSRF? What is the problem with the per-request token? Is login CSRF possible? Explain login CSRF? Have you ever exploited it? What is the mitigation for login CSRF? Suppose, in an application csrf token is implemented in each request and every request, except th

Lazy Hacker

Search This Blog