Kube Hunter couldn't find any clusters

[aquasecurity]

Kube Hunter couldn't find any clusters

[lizrice]

Thanks for raising. Just noting that the incorrect padding error may well come from base64 decoding. Needs investigation

[lmeyemezu]

Thanks for replying.
Do we need to do something on our side ?

[lmeyemezu]

Hi @lizrice
Any update ?
Regards

[hypery2k]

experencing the same error. sometimes getting the same error, but only in same cases. In most of the run it just works

[davidkarlsen]

no paddng problem - but can't find any cluster here either:

~ Started
~ Discovering Open Kubernetes Services...
|
| Accessed to pod's secrets:
|   type: vulnerability
|   host: None:None
|   description: 
|     Accessing the pod's secrets within a
|     compromised pod might disclose valuable data to a
|_    potential attacker

----------


Kube Hunter couldn't find any clusters

Using this chart: https://github.com/helm/charts/tree/master/stable/kube-hunter

[ImPurshu]

~ Started
~ Discovering Open Kubernetes Services...
|
| Accessed to pod's secrets:
| type: vulnerability
| host: None:None
| description:
| Accessing the pod's secrets within a
| compromised pod might disclose valuable data to a
|_ potential attacker
Cannot read wireshark manuf database

Same error I am facing.
Any idea?

[jayunit100]

same here, kubectl create -f job.yml, then the logs:

~ Started
~ Discovering Open Kubernetes Services...
|
| Accessed to pod's secrets:
|   type: vulnerability
|   host: None:None
|   description:
|     Accessing the pod's secrets within a
|     compromised pod might disclose valuable data to a
|_    potential attacker
----------
Kube Hunter couldn't find any clusters

[aakarshit-batchu]

Hi Guys,
Facing the same issue here with kube-hunter pod batch job.

`
~ Started
~ Discovering Open Kubernetes Services...
|
| Read access to pod's service account token:
| type: vulnerability
| host: None:None
| description:
| Accessing the pod service account token
| gives an attacker the option to use the
|_ server API
|
| Access to pod's secrets:
| type: vulnerability
| host: None:None
| description:
| Accessing the pod's secrets within a
| compromised pod might disclose valuable data to a
|_ potential attacker
Cannot read wireshark manuf database

Kube Hunter couldn't find any clusters
`

Kindly help me with this issue.

[Richahasija]

i Guys,
Facing the same issue here with kube-hunter remote scanning

~ Started
~ Discovering Open Kubernetes Services...

Kube Hunter couldn't find any clusters

---

[jgsqware]

What is the correct format kube-hunter is expecting?

[MysteriousNeo]

Any update on this bug , i want to run kube hunter in my cluster.

[sachsachdeva]

Facing the same Issue, I tried this on the AKS cluster today

~ Started
~ Discovering Open Kubernetes Services...
|
| Accessed to pod's secrets:
| type: vulnerability
| host: None:None
| description:
| Accessing the pod's secrets within a
| compromised pod might disclose valuable data to a
|_ potential attacker

---

[davidkarlsen]

Is this project dead?

[lizrice]

Far from it! Note that not being able to find any clusters is a perfectly plausible response - for example if the cluster is not accessible over the network from where kube-hunter is run.

Please run with logging turned on @sachsachdeva so we can get some clues. Also @danielsagi to re-test on AKS when you have a chance.

[danielsagi]

@sachsachdeva @aakarshit-batchu @davidkarlsen please see #140.
This fixes the issue in your case of not printing the vulnerabilities found from running with job.yaml.

@lmeyemezu After: #137 exceptions are now logged correctly, so if you would run now, we can debug and see the origin of the "incorrect padding" error you got, also, there has been multiple PR's regarding the exceptions, from when this issue was posted, so theres a good chance it was fixed.
if the problem consists in reproduction, please open a new issue, with the output of the debug messages of "incorrect padding"