Improper Cache Control

Improper Cache Control | Report Data

Analysis:

During the analysis, it was observed that the application didn’t implement cache control directives properly in its response headers because of which the browser was storing sensitive internal pages in its cache. Please refer to the below-provided evidence and proof of concept:

Impact:

This vulnerability can be exploited by an attacker having access to the victim's computer by browsing the cached pages. After getting access to sensitive information, the attacker can misuse the information.

Recommendation:

It is recommended to implement all Cache-Control directives properly. The following solutions are recommended to fix the vulnerability:

I. Multiple mechanisms, including HTTP headers and Meta tags, should be used to ensure that the pages containing sensitive information are not cached by user's browsers.

II. Authenticated pages should be marked with all the variants of the no-cache tag to prevent someone from using the browser's back button to access the history. Some of the tags are:

· Cache-control: private

· Cache-control: no-cache

· Cache-control: no-store

· Cache-control: pre-check=0

· Cache-control: post-check=0

· Cache-control: must-revalidate

· Pragma: no-cache

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