HTTPS not enforced at dex.sifchain.finance
Low
Vulnerability Details
Hi
The requestes using non secured `HTTP` do not automatically upgraded to HTTPS , The impact of this an attacker can laucn a MITM attack and steal users information.
## Impact
Data sent over HTTP, is being transmitted in plain , sniffers can see it , edit it , poison ads , know what contents being surfed by Buzzfeed users.
**Reproduce**
*Use Curl to check the response*
```
curl -i -s -k -X 'GET' \
-H 'User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:49.0) Gecko/20100101 Firefox/49.0' \
'http://dex.sifchain.finance'
```
#Fix
When a resource is requested using `http` your server should automatically upgrade the request to `HTTPS`
Get `http://dex.sifchain.finance`
the response should be
```
HTTP/1.1 301 Moved Permanently
Location: https://dex.sifchain.finance/
```
**Other hosts**
```
http://x.sifchain.finance/
http://bn.sifchain.finance/
http://dex.sifchain.finance/
http://blockexplorer.sifchain.finance/
http://sandpit.sifchain.finance/
http://dex.sifchain.finance/
http://blockexplorer-merry-go-round.sifchain.finance/
http://blockexplorer.sifchain.finance/
http://blockexplorer-testnet.sifchain.finance/
```
#Ref
- https://www.owasp.org/index.php/Man-in-the-middle_attack
- https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet
- https://www.owasp.org/index.php/HTTP_Strict_Transport_Security_Cheat_Sheet
- https://www.owasp.org/index.php/Testing_for_SSL-TLS_(OWASP-CM-001)
Regards
Actions
View on HackerOneReport Stats
- Report ID: 1126401
- State: Closed
- Substate: not-applicable
- Upvotes: 1