Full Disclosure mailing list archives
Glype proxy privacy settings can be disabled via CSRF
From: "Securify B.V." <lists () securify nl>
Date: Mon, 22 Sep 2014 18:52:35 +0200
------------------------------------------------------------------------ Glype proxy privacy settings can be disabled via CSRF ------------------------------------------------------------------------ Securify, September 2014 ------------------------------------------------------------------------ Abstract ------------------------------------------------------------------------ A path traversal vulnerability has been identified in the Glype web-based proxy that allows an attacker to run arbitrary PHP code on the server or to remove critical files from the filesystem. This only affects servers that are configured to: - store Glype cookies locally; AND - disable PHP display_errors; AND - allow the webserver process to write to the filesystem (document root). ------------------------------------------------------------------------ Affected versions ------------------------------------------------------------------------ This issue has been identified in Glype 1.4.9. Older version are most likely affected as well. ------------------------------------------------------------------------ Fix ------------------------------------------------------------------------ Glype was informed and a fixed version (1.4.10) is now available at www.glype.com ------------------------------------------------------------------------ Details ------------------------------------------------------------------------ http://www.securify.nl/advisory/SFY20140902/glype_proxy_privacy_settings_can_be_disabled_via_csrf.html _______________________________________________ Sent through the Full Disclosure mailing list http://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/
Current thread:
- Glype proxy privacy settings can be disabled via CSRF Securify B.V. (Sep 22)
- <Possible follow-ups>
- Glype proxy privacy settings can be disabled via CSRF Securify B.V. (Sep 22)