-
Notifications
You must be signed in to change notification settings - Fork 52
Improve NTLM Collection Logging BED-7374 #272
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
Open
lrfalslev
wants to merge
8
commits into
v4
Choose a base branch
from
lfalslev/bed-7374
base: v4
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
e8cb013
add compstatus to registryprocessor
lrfalslev 53a2e0f
add RegistryProcessorTests
lrfalslev 9019d99
null handling
lrfalslev 221ce52
clean up compstatus log
lrfalslev 9383031
fact attribute
lrfalslev 9350ffe
include registry strategy in successful compstat log
lrfalslev dd88aa0
use strategy name in log
lrfalslev b4939bb
include successful strategy in result
lrfalslev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,16 @@ | ||
| #nullable enable | ||
| namespace SharpHoundRPC.Registry { | ||
| using System.Collections.Generic; | ||
|
|
||
| using System; | ||
| using System.Collections.Generic; | ||
|
|
||
| namespace SharpHoundRPC.Registry { | ||
|
|
||
| public class StrategyExecutorResult<T> { | ||
| public IEnumerable<T>? Results { get; set; } = null; | ||
| public IEnumerable<StrategyResult<T>>? FailureAttempts { get; set; } = null; | ||
| public bool WasSuccessful = false; | ||
| public Type? SuccessfulStrategy { get; set; } = null; | ||
| } | ||
| #nullable disable | ||
| } | ||
| } | ||
|
|
||
| #nullable disable |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 720
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 241
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 1154
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 2263
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 457
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 982
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 1991
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 1705
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 780
🏁 Script executed:
Repository: SpecterOps/SharpHoundCommon
Length of output: 3475
Fragile strategy-name resolution via index arithmetic.
Line 94 infers the successful strategy by indexing
_strategies[collectedData.FailureAttempts?.Count() ?? 0]. This silently couplesRegistryProcessorto the internal iteration order ofStrategyExecutorand the exact composition of_strategies. IfStrategyExecutorever skips a strategy without recording a failure attempt, reorders strategies, or if_strategiesis modified independently, this will silently report the wrong strategy name—or throwIndexOutOfRangeException.The successful strategy type is available in
StrategyExecutor.CollectAsyncat the point of success but is never captured in the result. Add aSuccessfulStrategyTypeproperty toStrategyExecutorResult<T>and set it on the success path, then use that instead of array indexing.Proposed fix in StrategyExecutorResult
In
StrategyExecutorResult.cs:public class StrategyExecutorResult<T> { public IEnumerable<T>? Results { get; set; } = null; public IEnumerable<StrategyResult<T>>? FailureAttempts { get; set; } = null; public bool WasSuccessful = false; + public Type? SuccessfulStrategyType { get; set; } = null; }In
StrategyExecutor.cs, set it on the success path:return new StrategyExecutorResult<T> { Results = results, FailureAttempts = attempts, - WasSuccessful = true + WasSuccessful = true, + SuccessfulStrategyType = strategy.GetType() };Then in
RegistryProcessor.cs:await SendComputerStatus(new CSVComputerStatus { - Task = $"{nameof(ReadRegistrySettings)} - {_strategies[collectedData.FailureAttempts?.Count() ?? 0].GetType().Name}", + Task = $"{nameof(ReadRegistrySettings)} - {collectedData.SuccessfulStrategyType?.Name ?? "Unknown"}", ComputerName = targetMachine, Status = CSVComputerStatus.StatusSuccess });🤖 Prompt for AI Agents