Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Certifried?

Certifried is CVE-2022-26923, an Active Directory flaw that let any domain user create a machine account, claim a domain controller’s DNS name, and obtain a certificate authenticating as that controller.

Illustration for the cybersecurity term Certifried
Home / Blog / Cybersecurity Terms / What Is Certifried?
17 November 2026

What Is Certifried?

What Is Certifried?

Certifried is the name given by its discoverer, Oliver Lyak, to CVE-2022-26923: a privilege escalation vulnerability in Active Directory Domain Services, patched by Microsoft on 10 May 2022. It allowed any authenticated domain user, with no special rights whatsoever, to obtain a certificate that authenticated them as a domain controller. From there, full domain compromise follows in a single step.

It is one of the clearest illustrations of why certificate infrastructure deserves the same scrutiny as domain controllers themselves. Nothing in the attack involved a misconfigured template or a weak password. It used default settings, available out of the box in any forest running Active Directory Certificate Services.

The Chain of Defaults

Three separate defaults combine:

  1. Machine account quota. The ms-DS-MachineAccountQuota attribute is set to 10 in a default domain, meaning any authenticated user may create up to ten computer accounts.
  2. Control of your own object. The creator of a computer account becomes its owner and can write to its attributes, including dNSHostName.
  3. Certificate mapping by DNS name. The default Machine certificate template includes the dNSHostName value in the subject alternative name, and the Key Distribution Centre mapped an incoming certificate to an account by matching that name.

The attack simply walks the chain. Create a computer account. Clear the dNSHostName of the victim domain controller’s own account, or exploit the lack of uniqueness checking, and set your new machine’s dNSHostName to dc01.corp.example. Request a certificate from the Machine template, which any domain computer may enrol in. Authenticate with it. The KDC matches the DNS name, issues a ticket for the domain controller’s account, and the attacker can then perform DCSync and extract every credential in the domain.

The Fix: KB5014754

Microsoft’s May 2022 update addressed the root cause by changing how certificates map to accounts. Certificates issued by an enterprise CA now carry a new extension, szOID_NTDS_CA_SECURITY_EXT with object identifier 1.3.6.1.4.1.311.25.2, containing the security identifier of the requesting account. The KDC can then verify that the certificate was issued to the account it claims to represent, rather than trusting a name the requester supplied.

Because adding a mandatory new check would have broken smart card and third-party certificate deployments overnight, Microsoft staged the rollout. Domain controllers started in Compatibility mode, logging mismatches in events 39, 40, and 41 without blocking them; Full Enforcement mode, which rejects weakly mapped certificates outright, was repeatedly delayed before finally arriving. Many organisations patched, saw the audit events, and never completed the move to enforcement.

What to Check in Your Own Forest

Why It Still Appears in Reports

Testers continue to find exploitable forests, usually because a domain controller was rebuilt from an old image, because a child domain was never patched, or because the machine account quota was left at 10 and enforcement was never switched on. Certipy automates the whole sequence, so a tester with one standard user account can demonstrate the escalation in under a minute.

Active Directory and certificate services configuration review is part of our infrastructure security testing services, and this is one of the first things we look at.

FAQ – Frequently Asked Questions

Is Patching Alone Enough to Stop Certifried?

Installing the May 2022 update is necessary but not sufficient on its own. Domain controllers initially run in Compatibility mode, which logs weak certificate mappings rather than blocking them. Protection is complete only once strong certificate binding enforcement is set to full. Check the registry value on every domain controller rather than assuming the update changed it for you.

Why Should Machine Account Quota Be Zero?

The default of 10 lets any authenticated user create computer accounts, which is a prerequisite for Certifried and for several other Active Directory attacks, including resource-based constrained delegation abuse. Almost no organisation relies on ordinary users joining machines to the domain. Set the attribute to zero and grant the join right to a specific delegated group instead.

How Do I Find Weakly Mapped Certificates Before Enforcing?

After installing the update, review System log events 39, 40, and 41 on domain controllers. They identify certificates that would be rejected under full enforcement, together with the account involved. Typical sources are third-party smart card systems, network access control appliances, and older VPN deployments. Reissue those certificates so they carry the requester security identifier, then enable enforcement.

Does This Affect Entra ID or Only On-Premises AD?

The vulnerability is in on-premises Active Directory Domain Services and its certificate mapping, so cloud-only identities are not directly affected. Hybrid environments are, because compromise of the on-premises forest usually leads to the cloud tenant through synchronisation accounts, federation trust, or privileged users whose credentials exist in both places.

Related Terms

You May Be Interested In These

What Is Non-Repudiation?

Cybersecurity Terms

17 November 2026

What Is Non-Repudiation?

Read More
What Is a Software Bill of Materials (SBOM)?

Cybersecurity Terms

17 November 2026

What Is a Software Bill of Materials (SBOM)?

Read More
What Is TACACS+?

Cybersecurity Terms

17 November 2026

What Is TACACS+?

Read More