New attack technique: Usage of SendSerialConsoleSSHPublicKey on multiple instances #599
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?
Motivation
I saw that this was an open and prioritized issue #487
There are multiple reports of this technique being exploited in the wild.
To exploit SendSerialConsoleSSHPublicKey, an attacker must first enable EC2 Serial Console access. I did not enable this in the warm-up phase because Permiso has observed this behavior as part of a larger attack. In their report, Permiso describes how attackers enable EC2 Serial Console access in compromised AWS accounts and then attempt to use SendSerialConsoleSSHPublicKey.
If EC2 Serial Console access is already enabled, I leave it as is to avoid disabling it.
I'm not sure if there is an automation to generate the logs with Grimoire, so I haven't added this.
Checklist