Closed kenmayo closed 3 months ago
Initial Configuration checks on likely sources of this vulnerability indicate proper configuration for most EC2 instances. The XFRAME headers are being explicitly added with the SAMEORIGIN
option or the DENY
option. In some cases, HTTP to HTTPS redirects cover the vulnerability regardless for the port 80 since it forces the use of HTTPS, making the call respect the XFRAME headers.
Will verify the legacy proxies just in case. Will also verify the cluster web services as well.
Team has decided to request a new scan due to the potential of having this vulnerability addressed already. The infrastructure has changed drastically since this scan was performed.
Scan that was requested will take a while.
Closing
Please resolve this finding NLT 7/10/24