Sophos Web Appliance Session Fixation

Sophos Web Appliance version suffers from a session fixation vulnerability.

MD5 | 54ffcfe60969b3b8b5f25ffdd8ec5057

# Exploit Title: [Sophos Secure Web Appliance Session Fixation Vulnerability]
# Date: [28/02/2017]
# Exploit Author: [SlidingWindow] , Twitter: @Kapil_Khot
# Vendor Homepage: []
# Version: [Tested on Sophos Web Appliance version Older versions may also be affected]
# Tested on: [Sophos Web Appliance version]
# CVE : [CVE-2017-6412]
# Vendor Security Bulletin:

Sophos Secure Web Appliance is a purpose-built secure web gateway appliance which makes web protection simple. It provides advanced protection from todayas sophisticated web malware with lightning performance that wonat slow users down. You get full control and instant insights over all web activity on your network.

Session Fixation Vulnerability

#Vulnerability Details:-

#1. Session Fixation Vulnerability (CVE-2017-6412)

A remote attacker could host a malicious page on his website that makes POST request to the victimas Sophos Web Appliance to set the Session ID using STYLE parameter. The appliance does not validate if the Session ID sent by user/browser was issued by itself or fixed by an attacker.

Also, the appliance does not invalidate pre-login Session IDs it issued earlier once user logs in successfully. It continues to use the same pre-login Session ID instead of invalidating it and issuing a new one.

Note: An attacker would have to guess/know the IP address of the victim's device


1.Visit the Sophos Login page to obtain pre-auth Session ID.

2.Host following webpage on attacking machine with the Session ID obtained in #1. It can be changed a little bit.

<form name="Sophos_Login"action="" method="POST" >
<input type="hidden" name="STYLE" value="Pre-Auth Session ID">

window.onload = function(){

3. Visit the above page another machine.

4. You will be redirected to the login page, however Session ID will be the same.

5. Log into the appliance and check the Session ID, it will be the same from #1.

#Vulnerability Disclosure Timeline:

28/02/2017: First email to disclose the vulnerability to the vendor
28/02/2017: Vendor requested a vulnerability report
28/02/2017: Report sent to vendor.
28/02/2017: Vendor validated the report and confirmed the vulnerability
01/03/2017: CVE MITRE assigned CVE-2017-6412 to this vulnerability
03/03/2017: Vendor confirms that the fix is ready and is in the process of testing.
09/03/2017: Vendor confirmed that the patch will be released on March 17 2017 and requested to hold off publishing the CVE until March 31 2017.
17/03/2017: Vendor released the patch:
31/03/2017: Published CVE as agreed by vendor

Related Posts