This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 26
As an Internal Attacker... #38
Labels
scenario
describes a scenario or scenarios for a test
Comments
Scanning the Kubespray hosts within the cluster, we are able to access the
|
Odd permissions within the mounted serviceaccount directory (which is mounted by default):
EDIT (added by @disconnect3d ):
|
We are able to access kubelet logs leveraging the default service token from within a container:
|
Scanning from within the docker container (cut out early, need to try again):
|
At least part of this captured as TOA-K8S-031 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
Internal Attacker is a position such that an unprivileged attacker has successfully transited external boundaries, and has established themselves on an internal resource, such as a container.
Setup
I wish to map my env
I wish to escalate privileges
The text was updated successfully, but these errors were encountered: