-
Notifications
You must be signed in to change notification settings - Fork 786
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
Exploit timeline #2455
Merged
Merged
Exploit timeline #2455
Conversation
This file contains 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
shreyamalviya
force-pushed
the
2430-exploit-timeline
branch
2 times, most recently
from
October 19, 2022 11:22
588c0a9
to
9bc71d7
Compare
shreyamalviya
force-pushed
the
2430-exploit-timeline
branch
from
October 19, 2022 11:27
9bc71d7
to
4061460
Compare
shreyamalviya
force-pushed
the
2430-exploit-timeline
branch
from
October 19, 2022 11:30
4061460
to
1d939f5
Compare
cakekoa
force-pushed
the
2430-exploit-timeline
branch
from
October 19, 2022 17:46
1d939f5
to
c71722c
Compare
cakekoa
force-pushed
the
2430-exploit-timeline
branch
from
October 19, 2022 18:11
c71722c
to
1bba0a5
Compare
Codecov ReportBase: 60.98% // Head: 60.98% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## develop #2455 +/- ##
========================================
Coverage 60.98% 60.98%
========================================
Files 547 547
Lines 14502 14502
========================================
Hits 8844 8844
Misses 5658 5658 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
cakekoa
force-pushed
the
2430-exploit-timeline
branch
from
October 19, 2022 20:48
3ac2f45
to
cddafab
Compare
…ttempts in MapPageWrapper.tsx
…tempts were found, in PreviewPane.js
Fetching thousands of events every second will make the map less responsive. It's better to only fetch it once we need it (upon clicking the node)
Each map node only had one agentID, while in reality multiple agents could've run. By saving all agents into mapNode we can figure out which agent belongs to which machine
mssalvatore
approved these changes
Oct 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Fixes a part of #2430
PR Checklist
Was the documentation framework updated to reflect the changes?Testing Checklist
Added relevant unit tests?Node vulnerable to Zerologon
Node vulnerable to SMB
Island node