16 ms·
it was not, read again
by deepwell 7y ago
it was not, read again
- Perceptes 7y agoBut it does seem to be the case that the same SSH key pair that was used to access Jenkins also provided access to the production infrastructure. Unless I'm misunderstanding the nature of the attack.
- zigara 7y agoIt seems the issue was developers using SSH agent forwarding which was abused to access the production environment.