Take a look in the Email I got from Google a few minutes ago:
We are writing to inform you of a potential security issue with Website Optimizer. By exploiting a vulnerability in the Website Optimizer Control Script, an attacker might be able to execute malicious code on your site using a Cross-Site Scripting (XSS) attack. This attack can only take place if a website or browser has already been compromised by a separate attack. While the immediate probability of this attack is low, we urge you to take action to protect your site.
We have fixed the bug, and all new experiments are not susceptible. However, any experiments you are currently running need to be updated to fix the bug on your site. Additionally, if you have any Website Optimizer scripts from paused or stopped experiments created before December 3, 2010, you will need to remove or update that code as well.
There are two ways to update your code. You can either stop current experiments, remove the old scripts, and create a new experiment, or you can update the code on your site directly. We strongly recommend creating a new experiment as it is the simpler method.
Creating a New Experiment
- Stop any currently running Website Optimizer experiments
- Remove all the Website Optimizer scripts from your site
- Create a new experiment as normal. New experiments are not vulnerable.
Updating the Website Optimizer Control Script Directly
- Locate the Control Script on your site. It looks like this:
A/B Test Control Script
> Multivariate Test Control Script
1. Locate the following in the Control Script: `return c.substring(...`
2. Modify the following line as shown:
BEFORE: `return c.substring(i+n.length+1,j<0?c.length:j)`
FIXED: `return escape(c.substring(i+n.length+1,j<0?c.length:j))`
Make sure to include the final closing parenthesis “)”
> Fixed A/B Control Script
> Fixed Multivariate Control Script
Note that the
k=XXXXXXXXX` line in the above Control Script examples is a placeholder.
> Your experiment will continue as normal after you’ve made this update. There’s no need to pause or restart the experiment.
> We’re committed to keeping Website Optimizer secure, and we’re deeply sorry for this issue. We will continue to work hard to prevent future vulnerabilities.
> Google Website Optimizer Team