The security of our customers and their applications is of the highest importance to Microsoft. As you may know, we have a process called the Security Development Lifecycle. You can click here to learn more about it. As part of that internal process, we recently discovered an issue with the Windows Azure Software Development Kit (SDK). As soon as it was discovered, our teams worked quickly to fix it and release a refresh of the SDK. This blog post provides guidance on this issue.
This refresh of the Windows Azure November 2010 SDK (SDK 1.3) resolves an issue that affects applications developed using SDK v1.3. We are encouraging affected customers to install the refresh of the SDK and redeploy their application(s).
Who is affected?
This issue affects applications developed using ASP.NET and using the new "Full IIS" feature of SDK v1.3 that have a Web Role deployed. "Web Role" is defined as a single HTTP endpoint and a single HTTPS endpoint for external clients. This is not to be confused with the "Worker Role," which is defined as up to five external endpoints using HTTP, HTTPS or TCP. Each external endpoint defined for a role must listen on a unique port.
Applying the fix
To apply the fix:
1. Download and install the refresh of the November 2010 Tools and SDK (recommended).
After you've applied the fix, you'll have to re-package your service and then upgrade or re-deploy your service in the cloud.
Verifying the fix
To verify the fix has been applied:
1. Check the version number of 'Windows Azure SDK' after upgrading to this refresh, as displayed under 'Programs and Features.' It should be 1.3.20121.1237.