TLS POODLE vulnerability when using SSL LABS to check SSL security

I used a script to secure my SSL connection to remove the old SSL V2 and V3 as well as moving the stronger ciphers to the told and removing the old weak ciphers.

However, SSL LABS kept telling me I was vulnerable to PODDLE. I didn't know why since i removed SSL V3 (which essentially should remove any PODDLE attacks).

After further inspection it was saying that my TLS was vulnerable to POODLE. After much research I found out i needed, Windows6.1-KB2655992-x64. I am running Windows 2008 R2 but this patch fixes some TLS vulnerbilities and it fixed my TLS POODLE issue. I don't think thats what the patch is for, but it does fix it.

The patch also has versions for Windows 7, 32 bit versions of Windows 2008, etc.


Microsoft Bulletin

Granting access to admin$

Recently Microsoft has been taking security serious (well, they are at least trying). For those of you who have installed Exchange 2010 you know what I'm talking about. Previously when installing Windows (or Exchange) everything was wide open. Pretty much an "enable everything, close it later if you don't want it" type of mentality. Lately they have been closing or disabling services, not installing all components unless needed and turning on all software firewalls.

Recently I was installing software from a server that needed to connect to the admin$ share on a computer and install components. So i did my usual:

net share admin$ /users:5


I was able to connect but couldn't make a directory. After looking at the help I needed to add the admin$ share using this command:

net share admin$ /users:5 /grant:username,full


username being either a local or domain username. If using a domain username make sure to put the domain name followed by a backslash and then the username (ie, contesto\bsmith)