Skip to content

Commit de15d1e

Browse files
committed
Minor doc update
1 parent e88883c commit de15d1e

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

docs/metasploit-framework.wiki/ad-certificates/Attacking-AD-CS-ESC-Vulnerabilities.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1115,7 +1115,6 @@ msf6 auxiliary(admin/dcerpc/esc_update_ldap_object) > run
11151115
We can then use the `kerberos/get_ticket` module to gain a Kerberos ticket granting ticket (TGT) as the `Administrator`
11161116
domain administrator. See the [Getting A Kerberos Ticket](#getting-a-kerberos-ticket) section for more information.
11171117

1118-
11191118
## ESC9 Scenario 2
11201119
Pre-requisites:
11211120
- `StrongCertificateBindingEnforcement` is set to `1` (if it's set to `0` exploitation will still work but technically you're exploiting ESC10 in that case)
@@ -1130,7 +1129,6 @@ We will be changing the `dNSHostName` of the machine account `Test1$` to `DC2.ke
11301129

11311130
`CERT_TEMPLATE` will be set to `ESC9-Template-Dns` which is the same template as `ESC9-Template` but with the `SubjectAltRequireDNS` flag set instead of the `SubjectAltRequireUPN` flag.
11321131

1133-
11341132
```
11351133
msf6 auxiliary(admin/dcerpc/esc_update_ldap_object) > set rhosts 172.16.199.200
11361134
rhosts => 172.16.199.200
@@ -1319,7 +1317,6 @@ Active sessions
13191317
13201318
```
13211319

1322-
13231320
# Exploiting ESC13
13241321
To exploit ESC13, we need to target a certificate that has an issuance policy linked to a universal group in Active
13251322
Directory. Unlike some of the other ESC techniques, successfully exploiting ESC13 isn't necessarily guaranteed to yield

documentation/modules/auxiliary/admin/dcerpc/esc_update_ldap_object.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,10 +60,10 @@ An alternate DNS hostname to set for the target user, e.g., `host.domain.local`.
6060
1. Set `TARGET_USERNAME` to the user you want to update and then request a certificate for
6161
1. Set the `UPDATE_LDAP_OBJECT` to either `userPrincipalName` or `dNSHostName` depending on the scenario you are exploiting
6262
1. Set the `UPDATE_LDAP_OBJECT_VALUE` to the value you want to set for the `UPDATE_LDAP_OBJECT`, e.g., `Administrator`
63-
2. Set `CA` to the name of the CA you want to request a certificate and `cert_template` to the name of the certificate template you want to use
63+
1. Set `CA` to the name of the CA you want to request a certificate and `cert_template` to the name of the certificate template you want to use
6464
1. Run the module
6565
1. This should update the LDAP object attribute and request a certificate for the target user, which will be saved as a .pfx file.
66-
2. If the target is vulnerable to the scenario you are exploiting, the pfx file will allow for privilege escalation.
66+
1. If the target is vulnerable to the scenario you are exploiting, the pfx file will allow for privilege escalation.
6767

6868
## Scenarios
6969

0 commit comments

Comments
 (0)