Hacking Articles Tips Tricks Videos Tutorials
470 subscribers
65.9K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
How to useInstall KubeEye on your machineDownload pre built executables from Releases (https://github.com/kubesphere/kubeeye/releases).Or you can build from source codeNote: make install will create kubeeye in /usr/local/bin/ on your machine.git clone https://github.com/kubesphere/kubeeye.git
cd kubeeye
make installke[Optional] Install Node-problem-Detector (https://github.com/kubernetes/node-problem-detector)Note: This will install npd on your cluster, only required if you want detailed report.kubeeye install npdRun KubeEyeNote: The results of kubeeye sort by resource kind.kubeeye audit
KIND NAMESPACE NAME REASON LEVEL MESSAGE
Node docker-desktop kubelet has no sufficient memory available warning KubeletHasNoSufficientMemory
Node docker-desktop kubelet has no sufficient PID available warning KubeletHasNoSufficientPID
Node docker-desktop kubelet has disk pressure warning KubeletHasDiskPressure
Deployment default testkubeeye NoCPULimits
Deployment default testkubeeye NoReadinessProbe
Deployment default testkubeeye NotRunAsNonRoot
Deployment kube-system coredns NoCPULimits
Deployment kube-system coredns ImagePullPolicyNotAlways
Deployment kube-system coredns NotRunAsNonRoot
Deployment kubeeye-system kubeeye-controller-manager ImagePullPolicyNotAlways
Deployment kubeeye-system kubeeye-controller-manager NotRunAsNonRoot
DaemonSet kube-system kube-proxy NoCPULimits
DaemonSet k ube-system kube-proxy NotRunAsNonRoot
Event kube-system coredns-558bd4d5db-c26j8.16d5fa3ddf56675f Unhealthy warning Readiness probe failed: Get "http://10.1.0.87:8181/ready": dial tcp 10.1.0.87:8181: connect: connection refused
Event kube-system coredns-558bd4d5db-c26j8.16d5fa3fbdc834c9 Unhealthy warning Readiness probe failed: HTTP probe failed with statuscode: 503
Event kube-system vpnkit-controller.16d5ac2b2b4fa1eb BackOff warning Back-off restarting failed container
Event kube-system vpnkit-controller.16d5fa44d0502641 BackOff warning Back-off restarting failed container

___________________________
@hacking_Attack
@Hacking_Video
Event kubeeye-system kubeeye-controller-manager-7f79c4ccc8-f2njw.16d5fa3f61b28527 Failed warning Error: ImagePullBackOff
Role kubeeye-system kubeeye-leader-election-role CanDeleteResources
ClusterRole kubeeye-manager-role CanDeleteResources
ClusterRole kubeeye-manager-role CanModifyWorkloads
ClusterRole vpnkit-controller CanImpersonateUser
ClusterRole vpnkit-controller CanDeleteResourcesWhat KubeEye can doKubeEye inspects cluster resources according with Kubernetes best practices, to make cluster stable.KubeEye can find problems of your cluster control plane, including kube-apiserver/kube-controller-manager/etcd, etc.KubeEye helps you detect all kinds of cluster nodes problems, including memory/cpu/disk pressure, unexpected kernel error logs, etc.ChecklistYES/NOCHECK ITEMDescriptionLevelPrivilegeEscalationAllowedPrivilege escalation (https://www.kitploit.com/search/label/Escalation) is alloweddangerCanImpersonateUserThe role/clusterrole can impersonate other userwarningCanModifyResourcesThe role/clusterrole can delete kubernetes resourceswarningCanModifyWorkloadsThe role/clusterrole can modify kubernetes workloadswarningNoCPULimitsThe resource does not set limits of CPU in containers.resourcesdangerNoCPURequestsThe resource does not set requests of CPU in containers.resourcesdangerHighRiskCapabilitiesHave high-Risk options in capabilities such as ALL/SYS_ADMIN/NET_ADMINdangerHostIPCAllowedHostIPC Set to truedangerHostNetworkAllowedHostNetwork Set to truedangerHostPIDAllowedHostPID Set to truedangerHostPortAllowedHostPort Set to truedangerImagePullPolicyNotAlwaysImage pull policy not alwayswarningImageTagIsLatestThe image tag is latestwarningImageTagMissThe image tag do not declaredangerInsecureCapabilitiesHave insecure options in capabilities such as KILL/SYS_CHROOT/CHOWNdangerNoLivenessProbeThe resource does not set livenessProbewarningNoMemoryLimitsThe resource does not set limits of memory in containers.resourcesdangerNoMemoryRequestsThe resource does not set requests of memory in containers.resourcesdangerNoPriorityClassNameThe resource does not set priorityClassNameignorePrivilegedAllowedRunning a pod in a privileged mode means that the pod can access the host’s resources and kernel capabilitiesdangerNoReadinessProbeThe resource does not set readinessProbewarningNotReadOnlyRootFilesystemThe resource does not set readOnlyRootFilesystem to truewarningNotRunAsNonRootThe resource does not set runAsNonRoot to true, maybe executed run as a root accountwarningCertificateExpiredPeriodCertificate expiration date less than 30 daysdangerEventAuditEvent auditwarningNodeStatusnode status auditwarningDockerStatusdocker status auditwarningKubeletStatuskubelet status auditwarningAdd your own inspection rulesAdd custom OPA rulescreate a directory (https://www.kitploit.com/search/label/Directory) for OPA rulesmkdir opaAdd custom OPA rules filesNote: the OPA rule for workloads, package name must be kubeeye_workloads_regofor RBAC, package name must be kubeeye_RBAC_regofor nodes, package name must be kubeeye_nodes_regoSave the following rules to rule file such as imageRegistryRule.rego to check the image registry address complies with rules.package kubeeye_workloads_rego

deny[msg] {
resource := input
type := resource.Object.kind
resourcename := resource.Object.metadata.name

___________________________
@hacking_Attack
@Hacking_Video
resourcenamespace := resource.Object.metadata.namespace
workloadsType := {"Deployment","ReplicaSet","DaemonSet","StatefulSet","Job"}
workloadsType[type]

not workloadsImageRegistryRule(resource)

msg := {
"Name": sprintf("%v", [resourcename]),
"Namespace": sprintf("%v", [resourcenamespace]),
"Type": sprintf("%v", [type]),
"Message": "ImageRegistryNotmyregistry"
}
}

workloadsImageRegistryRule(resource) {
regex.match("^myregistry.public.kubesphere/basic/.+", resource.Object.spec.template.spec.containers[_].image)
}Run KubeEye with custom rulesNote: Specify the path then Kubeeye will read all files in the directory that end with .rego.root:# kubeeye audit -p ./opa
NAMESPACE NAME KIND MESSAGE
default nginx1 Deployment [ImageRegistryNotmyregistry NotReadOnlyRootFilesystem NotRunAsNonRoot]
default nginx11 Deployment [ImageRegistryNotmyregistry PrivilegeEscalationAllowed HighRiskCapabilities HostIPCAllowed HostPortAllowed ImagePullPolicyNotAlways ImageTagIsLatest InsecureCapabilities NoPriorityClassName PrivilegedAllowed NotReadOnlyRootFilesystem NotRunAsNonRoot]
default nginx111 Deployment [ImageRegistryNotmyregistry NoCPULimits NoCPURequests ImageTagMiss NoLivenessProbe NoMemoryLimits NoMemoryRequests NoPriorityClassName NotReadOnlyRootFilesystem NoReadinessProbe NotRunAsNonRoot]Add custom NPD rulesedit configmapkubectl edit ConfigMap node-problem-detector-config -n kube-system restart NPD deploymentkubectl rollout restart DaemonSet node-problem-detector -n kube-systemKubeEye OperatorWhat is KubeEye OperatorKubeEye Operator is an inspection platform for Kubernetes, manage KubeEye by operator and generate inspection result.What KubeEye Operator can doKubeEye Operator provides management (https://www.kitploit.com/search/label/Management) functions through web page.KubeEye Operator recode inspection results by CR, can view and compare cluster inspection results by web page.KubeEye Operator provides more plugins.KubeEye Operator provides more detailed modification suggestions.deploy Kubeeyekubectl apply -f https://raw.githubusercontent.com/kubesphere/kubeeye/main/deploy/kubeeye.yaml
kubectl apply -f https://raw.githubusercontent.com/kubesphere/kubeeye/main/deploy/kubeeye_insights.yamlget the inspection resultskubectl get clusterinsight -o yamlapiVersion: v1
items:
- apiVersion: kubeeye.kubesphere.io/v1alpha1
kind: ClusterInsight
metadata:
name: clusterinsight-sample
namespace: default
spec:
auditPeriod: 24h
status:
auditResults:
auditResults:
- resourcesType: Node
resultInfos:
- namespace: ""
resourceInfos:
- items:
- level: warning
message: KubeletHasNoSufficientMemory
reason: kubelet has no sufficient memory available
- level: warning
message: KubeletHasNoSufficientPID
reason: kubelet has no sufficient PID available
- level: warning
message: KubeletHasDiskPressure
reason: kubelet has disk pressure
name: kubeeyeNodeDocumentsRoadMap (https://github.com/kubesphere/kubeeye/blob/main/docs/roadmap.md)FAQ (https://github.com/kubesphere/kubeeye/blob/main/docs/FAQ.md)

Download Kubeeye (https://github.com/kubesphere/kubeeye)

___________________________
@hacking_Attack
@Hacking_Video
hacking: security in practice
Haxxoring messenger group admin via html

So yeah basically I have been testing fbs messenger for a way to get round the dead (deleted accounts) admin in a chat. I managed to manipulate enough to get a "make admin button" and "remove member (scary sounding lol)" button, but I just haven't had the chance to locate a way to spoof admin privileges. I was wondering if anyone else has tried this or came across a workaround?

submitted by /u/Meatpoleexposer
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video
Unique Rate limit bypass worth 1800$

Proving the organization statement wrong with OOS Rate limit bypass.Continue reading on Medium »
Read more...