-
Notifications
You must be signed in to change notification settings - Fork 52
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
Got pfx from server with client auth #8
Comments
Hi @onSec-fr! Thanks for the issue; this has caused quite a stir over at the Bloodhound Gang Slack! 😂 We are busy looking into the full impact, but in the meantime to answer your questions: Great find, by the way. And thank you for raising an issue for this! |
Hi, thank you for your reply! indeed, it seems that this configuration is usual for mecm configured in PKI mode. Edit : @chrispanayi how can I join this slack channel ? I'd love to exchange ideas on these subjects :) |
@onSec-fr you can use this link -- https://ghst.ly/BHSlack Search for the #sccm channel once you're in there and this thread -- https://bloodhoundhq.slack.com/archives/C03N78QCRKJ/p1727407568588989 |
The link doesn't work for me ! |
Sorry for the delay @onSec-fr -- please try this one: https://join.slack.com/t/bloodhoundhq/shared_invite/zt-1tgq6ojd2-ixpx5nz9Wjtbhc3i8AVAWw |
Hello,
During an engagement, I was surprised to find that the certificate retrieved by the tool from the SMSTSMediaPFX variable was the one of the PXE server, with its corresponding private key. In my case, the certificate is configured for both server and client authentication.
So I used this pfx to request a TGT for the server machine account and I'm now SYSTEM on it.
Thanks for your feedback
The text was updated successfully, but these errors were encountered: