github/kube-hunter
1
0
Fork 0
mirror of https://github.com/aquasecurity/kube-hunter.git synced 2026-05-11 03:37:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

minor changes to readme, added categories to vulnerabilities

Browse Source
This commit is contained in:
daniel_sagi
2018-07-18 19:40:56 +03:00
parent 47d4263860
commit 45ab93fc26
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@@ -18,7 +18,6 @@ To specify remote machines for hunting, you can use the `--remote` option. Examp
Active hunting is an option in which Kube Hunter will exploit vulnerabilities it finds, in order to explore for further vulnerabilities.
The main difference between normal and active hunting is that a normal hunt will never change state of the cluster, while active hunting can potentially do state-changing and harmful operations on the cluster.
When active, evidence of vulnerabilities will be added to the final report.
To active hunt a cluster, use the `--active` flag. Example:
`./kube-hunter.py --remote some.domain.com --active`

8
src/README.md
View File

@@ -112,8 +112,9 @@ lets see some examples of creating different types of events:
```python
class ExposedMasterCN(Vulnerability, Event):
"""Explanation about this vulnerability and what it can do when exploited"""
def __init__(self):
Vulnerability.__init__(self, component=KubernetesCluster, name="Master Exposed From Certificate")
def __init__(self, master_ip):
Vulnerability.__init__(self, component=KubernetesCluster, name="Master Exposed From Certificate", category=InformationDisclosure)
self.evidence = master_ip
```
### Service
@@ -174,4 +175,5 @@ If another Hunter subscribes to the events that this Hunter publishes, if can a
## Proving Vulnerabilities
The process of proving vulnerabilities, is the base concept of the Active Hunting.
To prove a vulnerability, create an `ActiveHunter` that is subscribed to the vulnerability, and inside of the `execute`, specify the `evidence` attribute of the event.
To prove a vulnerability, create an `ActiveHunter` that is subscribed to the vulnerability, and inside of the `execute`, specify the `evidence` attribute of the event.
*Note that you can specify the 'evidence' attribute without active hunting*