Must PetitPotam NTLM relay mitigation include changing your CA server's CDP & AIA extensions?

Heath Durrett 501 Reputation points
2021-10-14T08:25:23.103+00:00

We are looking to mitigate the PetitPotam vulnerability on our internal 2Tier active Directory CA hierarchy. There is a very clear MS document here...

https://support.microsoft.com/en-gb/topic/kb5005413-mitigating-ntlm-relay-attacks-on-active-directory-certificate-services-ad-cs-3612b773-4043-4aa9-b23d-b87910cd3429

The very first instruction says "We recommend enabling EPA and disabling HTTP on AD CS servers."

However...there are no additional instructions on editing the CDP / AIA extensions in the subordinate CA server config.

My question is - what happens to already issued certificates without HTTPS in their certificate configuration and surely we need to add HTTPS extensions to the Subordinate CA configuration?

I'm worried that simply following this document will have a detrimental affect on my PKI infrastructure?

Any advice, explanations would be most gratefully welcomed!

Regards,
durrie

Windows development | Internet Information Services
Windows for business | Windows Server | Devices and deployment | Configure application groups
0 comments No comments
{count} votes

Accepted answer
  1. Vadims Podāns 9,186 Reputation points MVP
    2021-10-14T20:30:46.123+00:00

    The answer is simply no, since CDP/AIA use unauthenticated access. There is no NTLM when you download CDP/AIA items from IIS, so they are not subject for this vulnerability and no changes are required in these extensions.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Limitless Technology 39,931 Reputation points
    2021-10-14T18:58:01.947+00:00

    Hello @Heath Durrett

    Basically all your HTTP certificates would stop working as you enable EPA, require SSL and disable HTTP over ADCS. This is the "modern" safety rule for your environment, not only for PetitPotam, but for many other attacks. It's been many years that most issuing instances have moved to the SSL protocol and HTTPS, however is true that some signing is still done on HTTP mostly for backwards compatibility and historical purposes.

    Hope this helps with your query,

    ------
    --If the reply is helpful, please Upvote and Accept as answer--

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.