Initial Linkerd service detection rules #153
Merged
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.
Provides a way to detect the Linkerd service mesh for Kubernetes (https://linkerd.io/) that can help expand the attack surface (and/or leak the whole delegation table if verbosity is on).
The
badruleone works by supplying an invalid delegation table rule and then inspecting the response for known headers and error messages.The
ssrfone tries to reach out to an external server and look for some known headers or the known response: this can be enhanced by issuing internal requests at169.254.169.254to try reach for cloud metadata as well.Let me know if i'm doing it right guys, keep up the good work!