-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for ESC15 #19538
Add Support for ESC15 #19538
Conversation
Thanks for your pull request! Before this can be merged, we need the following documentation for your module: |
6ed9de2
to
0e3eb45
Compare
5b97877
to
0a10ef1
Compare
dc6f98f
to
acd5c93
Compare
Would you be able to throw in a quick Or I'm also happy to wait for Christophe to pick up the |
Thanks! I haven't tested it yet, but it looks good to me. Regarding the |
Alright with the latest commit in place, I'm reporting all of the vulnerabilities that the module is capable of finding.
|
In the following example, the Client Authentication OID (1.3.6.1.5.5.7.3.2) is added which enables the certificate to be | ||
used for authentication to LDAP via SCHANNEL. The operator can then perform LDAP queries with the privileges of the user | ||
specified in the alternate UPN. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any LDAP module that can be used with this certificate as an example?
4ad9e3e
to
b87471c
Compare
See RFC4532 and ruby-ldap/ruby-net-ldap#425
b87471c
to
98f9112
Compare
Thanks for updating this @zeroSteiner! Everything looks good to me now. ScenariosCheck certificate template
Check ESC15 with
|
Release NotesThis adds support for ESC15 to three AD CS related modules. A template is added so the |
This adds support for ESC15 to various AD CS related modules. A template is added so the
ad_cs_cert_template
module can create and update templates to be vulnerable to ESC15 (downgrading the schema may not work and should be tested, but creating a net-new one does work). Fingerprinting is added to theldap_esc_vulnerable_cert_finder
module to identify templates that are vulnerable to ESC15. Finally, OIDs can be specified in theicpr_cert
module so a vulnerable template can be exploited by a user.Todo
icpr_cert
docs for the new optionDemo
Not sure why the session is showing up as from 127.0.0.1 to 127.0.0.1, but with the new ldap whoami changes, it shows that the certificate authenticated as the
MSFLAB\smcintyre
DA user and not theMSFLAB\mhatter
normal user who issued it.Testing Steps
ad_cs_cert_template
to create a vulnerable certificate using the new templateldap_esc_vulnerable_cert_finder
module to identify the new templateicpr_cert
module to issue a certificate1.3.6.1.5.5.7.3.2
(Client Authentication)ALT_UPN
option to specify a privileged userldap_login
module to authenticate using schannel to the server with the certificategetuid
command on the session and see that it is authenticated as the user specified in theALT_UPN
datastore argument when the cert was issued