This fix would not block the attack that we describe below, which does not involve any script. The proposal was based on the consideration that benign proxy error messages are valuable for troubleshooting network problems, but there is no compelling reason to allow scripts in error messages. When we reported this issue to a browser vendor, one of the vendor’s proposed fixes was to disable scripts in any 4xx/5xx error-response pages, and only render static HTML contents. The script will run in the HTTPS context of the victim server and compromise the confidentiality. In Section III.A, we have seen that the PBP proxy can supply a script in an error-response. Certifying a Proxy Page with a Real Certificate In the second attack, the proxy can authenticate to the HTTPS server as a logon user.Ī. In the first attack, the proxy’s own page can be certified with the trusted certificate of the HTTPS server that the browser intends to communicate. They target the authentication mechanisms in browsers. In this section, we show two attacks that can be accomplished entirely by static HTML contents. When a class of security problems is not always script-related, defense solutions should be explored more broadly. Typically, for script-based security issues, the defense solutions are along the line of disabling, filtering, or guarding scripts. Nevertheless, in order to better understand the potential threat of PBP, thinking beyond script-based attacks is very important.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |