Description of problem:
Cross-Frame Scripting (XFS) vulnerability can allow an attacker to load the vulnerable application inside an HTML iframe tag on a malicious page. The attacker could use this weakness to devise a Clickjacking attack to conduct
phishing, frame sniffing, social engineering or Cross-Site Request Forgery attacks.
Version-Release number of selected component (if applicable):
"X-Frame-Options" header should be present in header of each server response. It will inform web browsers whether it can be framed on certain sites.
Fixed in rebase to upstream 4.4.
How we can verify this?
How QE will verify this?
You should not be able to open IPA Web UI in a frame.
1. So create a simple webpage with iframe which points to IPA.
2. It should fail to load IPA.
[root@dhcp207-129 ~]# rpm -q ipa-server
Please find the attached screen shot and web page html used to test this.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.