{"name":"BREACH Avoider","slug":"baw-breach-avoider","version":"1.3","author":"Julio Potier","author_profile":"https://profiles.wordpress.org/juliobox/","requires":"3.9","tested":"4.3.34","requires_php":false,"requires_plugins":[],"rating":100,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":3},"num_ratings":3,"support_threads":0,"support_threads_resolved":0,"downloaded":3236,"last_updated":"2015-08-11 10:52pm GMT","added":"2013-08-29","homepage":"http://blog.secupress.fr/breach-avoider-comment-eviter-hack-https-48.html","sections":{"description":"

In August 2013, a new Web Vulnerability has been released, in some words : “HTTPS can be hacked in 30 seconds”.

If you’re using the HTTPS (TSL or SSL) at any level (admin, front, event for 1 page) you HAVE to protect your site against this flaw now.

How ? Just install this free plugin!

\n","installation":"

Extract the plugin folder from the downloaded ZIP file.
Upload Bthe folder to your /wp-content/plugins/ directory.
Activate the plugin from the “Plugins” page in your Dashboard.
Done!

You can (and i encourage you to do it) define 2 constant in wp-config.php file :

BBA_REPEATER : used by this plugin to add a new secret srting in each nonces (e number used once to create a secure token and avoid CSRF flaws), default is 2, min is 1, no max, just change it.

BBA_NONCE_LENGTH : From 4 to 32 with 10 for default value, you can modify the length the each nonces in WordPress, the longer, the better

Also, WordPress includes a “nonce_life” filter hook. Its default value is 1 day, i suggest you to low this value, like 12 hours or 6 hours (DAY_IN_SECONDS /2 or /4)

\n","faq":"\n

What is BREACH?

This means “Browser Reconnaissance & Exfiltration via Adaptive Compression of Hypertext”
\nRead this http://www.kb.cert.org/vuls/id/987798 and this http://breachattack.com/

How to protect against BREACH?

Some of these mitigations may protect entire applications, while others may only protect individual web pages.
\n1. Disable HTTP compression. (1)
\n2. Separate the secrets from the user input. (2)
\n3. Randomize the secrets in each client request. -> Done!
\n4. Mask secrets (effectively randomizing by XORing with a random secret per request). -> Done!
\n5. Protect web pages from CSRF attacks.
\n6. Obfuscate the length of web responses by adding random amounts of arbitrary bytes. -> Done!

(1) I do not recommand this because of lack of performance, at least, but you can do it yourself in you PHP.ini or .htaccess, google “how to disable http gzip compression”
\n(2) Can’t do this in WordPress.

Install this plugin and be protected as much as we can do in WordPress.

\n\n","changelog":"

1.3

11 aug 2015
4.3 support
Security hardening using wp_get_session_token() + hash_equals()

1.2

29 aug 2013
New problem with pack() now, use my own function.

1.1

29 aug 2013
hex2bin() is not always available, use a pack() instead

1.0

29 aug 2013
First release

\n"},"download_link":"https://downloads.wordpress.org/plugin/baw-breach-avoider.zip","screenshots":[],"tags":{"breach":"breach","https":"https","security":"security"},"versions":[],"donate_link":"https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RB7646G6NVPWU","icons":{"default":"https://s.w.org/plugins/geopattern-icon/baw-breach-avoider_bba2a0.svg"},"contributors":{"juliobox":"https://profiles.wordpress.org/juliobox/"}}

BREACH Avoider

Screenshots

Categories

Get New Themes & Resources