Skip to content
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

Proposed New Edge: SyncLAPSPassword #555

Closed
simondotsh opened this issue Jul 14, 2022 · 6 comments
Closed

Proposed New Edge: SyncLAPSPassword #555

simondotsh opened this issue Jul 14, 2022 · 6 comments
Labels

Comments

@simondotsh
Copy link
Contributor

Context

The combination of DS-Replication-Get-Changes and DS-Replication-Get-Changes-In-Filtered-Set at the root of a domain renders it possible for a principal to perform a directory synchronization (DirSync), and retrieve confidential and RODC filtered attributes, such as LAPS' ms-Mcs-AdmPwd. See technical details here.

Proposed New Edge

Name: SyncLAPSPassword.
Conditions: A principal has both DS-Replication-Get-Changes and DS-Replication-Get-Changes-In-Filtered-Set at the root of a domain.
Linked To: All LAPS-enabled computers.

While this does not follow the current way edges for DCSync are drawn, it avoids returning a path when a principal only has one of the two privileges; however, it could lead to missing this edge when a principal can, for instance, add themselves to a group that has the second needed privileges. Despite this, I still believe this is the more desirable way to implement it.

Contributing

If this edge is wanted, and the proposed way to implement it suits you, I can contribute the required changes, but will be waiting for the green light before doing so.

@rvazarkar
Copy link
Contributor

Hey @simondotsh ,

Thanks for the issue, we're going to discuss this internally and get back to you

@rvazarkar
Copy link
Contributor

rvazarkar commented Jul 26, 2022

Hey @simondotsh , we've decided to accept this feature. Let me know if you want to contribute the code, otherwise we'll try and roll this into our 4.2 changeset and credit you with the request

@simondotsh
Copy link
Contributor Author

Hi @rvazarkar,

I'll give it a go and report back when I created the pull requests.

@simondotsh
Copy link
Contributor Author

Hello @rvazarkar,

See the pull requests above for the contribution of this edge.

@rvazarkar
Copy link
Contributor

This is a phenomenal PR. Thanks for the work. We're most likely going to accept it as is and make a few changes on our end to better fit some stuff we're doing for the 4.2 release.

@rvazarkar
Copy link
Contributor

All the necessary changes have been merged into the respective 4.2 branches of the project. I'll close this when we've fully merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants