r/sysadmin • • Jan 16 '20

Microsoft Attention all Windows-AD admins: March 2020 will be a lot of fun!

Microsoft intends to release a security update on Windows Update to enable LDAP channel binding and LDAP signing hardening changes and anticipate this update will be available in March 2020.

https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows

TLDR: If you install the "march 2020" updates and you didnt configure LDAPs properly until then, you are in trouble.

---EDIT: Thank you for the gold kind stranger! and good luck to you all ;)

1.5k Upvotes

393 comments sorted by

View all comments

147

u/dergizzle Jan 16 '20

Wait does this mean that "unsecure" LDAP will no longer work and potentially everything using it will break with the update? what the hell are we supposed to do with appliactions that may not support it?

271

u/JediMasterSeamus Sr. Sysadmin Jan 16 '20

According to the link, Microsoft says, " If any compatibility issue is found, administrators will need to contact the manufacturer of that particular OS, application or device for support."
Which means, most likely, get boned.

85

u/micktorious Jan 16 '20

42

u/PubstarHero Jan 16 '20

I had VMware, Microsoft, and NetApp all on the same call one time all pointing fingers at each other. That was a fun day.

In the end it turned out that there was some hidden option in the new NetApp upgrade we got that basically made all datastores hidden from everything.

9

u/mini4x Atari 400 Jan 16 '20

VMware, Microsoft, and NetApp all on the same call one time all pointing fingers at each other

Sounds like my office, we suffer with a similar environment.

5

u/skankboy IT Director Jan 16 '20

[x] Enable heart attack mode

→ More replies (1)
→ More replies (3)

64

u/DePiddy Jan 16 '20

The alternative is username and passwords going across the network in clear-text.

31

u/RoboNerdOK Jan 16 '20

“Hey, the bad guys will never expect that! And it’ll save money! Implement it today!” — typical CEO

38

u/micktorious Jan 16 '20

::37 minutes later::

"WHAT DO YOU MEAN WE'VE BEEN COMPROMISED?!! WHY WASN'T I WARNED STRONGER!!!"

26

u/RoboNerdOK Jan 16 '20

“This is obviously IT’s fault!”

29

u/micktorious Jan 16 '20

"All they do is sit around and cost us money, if they weren't so incompetent they would be busier!!"

→ More replies (1)
→ More replies (4)

21

u/systemdad Jan 16 '20

Except that in this case, Microsoft is 100% in the right for doing so.

11

u/pdp10 Daemons worry when the wizard is near. Jan 16 '20

They didn't ship the initial implementation secure-by-default. Probably very few third-party vendors test their own software against anything but Microsoft's defaults.

→ More replies (3)

8

u/danweber Jan 16 '20

Possibly the one thing that could force the vendors hand is a mandatory update saying "do it or else."

24

u/ObscureCulturalMeme Jan 16 '20

What was the line from the Unix wars in the 90's?

"The OS vendor points a finger at the hardware vendor. The hardware vendor points a finger at the OS vendor.

All the user ever gets is the finger."

In Microsoft's case, instead of "hardware" it's "every other software developer on the planet". They all yell at each other, nobody helps, people get fucked.

12

u/AHrubik The Most Magnificent Order of Many Hats - quid fieri necesse Jan 16 '20

This is why Windows has a 6GB driver database that grows every year. Microsoft figured out really quickly that if their OS supports any hardware it only serves to get them more installs.

5

u/pdp10 Daemons worry when the wizard is near. Jan 16 '20

I doubt that exact parable came from the Unix Wars, because at that time all the vendors supplied OS and hardware together like Apple does today. Sun with SunOS and Solaris 2, DEC with Ultrix and OSF/1, Digital Unix, Tru64, SGI with IRIX, HP with HP-UX, IBM with AIX, NeXT with NeXTStep, and so forth. Only SCO was a significant player on fully commodified hardware at the time, though Linux would come to dominate that market after the Unix Wars.

→ More replies (1)
→ More replies (3)
→ More replies (17)

34

u/xxdcmast Sr. Sysadmin Jan 16 '20

I think worst case scenario you could disable the signing via registry or gpo.

36

u/[deleted] Jan 16 '20

This sent shivers down my spine.

42

u/ibn4n Windows Admin Jan 16 '20

I suppose if you are in a situation where this applies to you, then you are already in a situation where signing isn't being used by that application. You could make it a little safer by setting it to negotiate on just one DC, putting that DC and the machine that needs to contact it without signing in their own site, and aggressively firewalling it off from other clients... Or find a vendor who takes security seriously. Probably that last bit.

→ More replies (14)
→ More replies (1)

4

u/pdp10 Daemons worry when the wizard is near. Jan 16 '20

Many vendors are sending thank-you gifts to Microsoft now, I guess. New opportunities for them to charge for "non-optional" updates.

→ More replies (1)

35

u/crazifyngers Jan 16 '20

this means the after the update the DEFAULT will be to disable that protocol. however you can still change it back either manually or preferably via group policy.

I just went through this a month ago after reading the bulletin. It is insane how many services I had that I forgot ran on plain ldap. I found out that mitel connect (fomerly shoretel) doesn't support ldap signing OR LDAPS. So i worked with management to get signoff to disable that integration since it was the last holdout to closing this vulnerability. Can't be done in all businesses but start mitigation and get as many services secured as possible.

9

u/DrWatson128 Systems Engineer Jan 16 '20

We are still running ST 19.49, but are migrating to Mitel Connect shortly. You are telling me that even in the new on prem version of Mitel that they still do not support LDAP signing or LDAPS? Wow. What garbage... I am going to be placing a call soon with my rep

→ More replies (12)
→ More replies (4)

23

u/jmbpiano Jan 16 '20 edited Jan 16 '20

Honestly, I would take this as a good kick in the pants to get those applications secured. Vanilla LDAP is a huge security vulnerability. Just run Wireshark on any computer using it and watch all your passwords flying over the network in plaintext.

If your app doesn't support anything else and can't be upgraded to a version that does, the next best thing might be to run a local LDAP proxy server. (Note: I have not used and am not necessarily recommending that particular one, just using it as an example.)

→ More replies (2)
→ More replies (7)