(https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/mounts.md) netpols Finds namespaces that do not have a default-deny network policy. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/netpols.md) nonroot Finds containers running as root. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/nonroot.md) privesc Finds containers that allow privilege escalation. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/privesc.md) privileged Finds containers running as privileged. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/privileged.md) rootfs Finds containers which do not have a read-only filesystem. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/rootfs.md) seccomp Finds containers running without Seccomp. docs (https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/seccomp.md) Global Flags Short Long Description --format The output format to use (one of "pretty", "logrus", "json") (default is "pretty") --kubeconfig Path to local Kubernetes config file. Only used in local mode (default is $HOME/.kube/config) -c --context The name of the kubeconfig context to use -f --manifest Path to the yaml configuration to audit. Only used in manifest mode. You may use - to read from stdin. -n --namespace Only audit resources in the specified namespace. Not currently supported in manifest mode. -g --includegenerated Include generated resources in scan (such as Pods generated by deployments). If you would like kubeaudit to produce results for generated resources (for example if you have custom resources or want to catch orphaned resources where the owner resource no longer exists) you can use this flag. -m --minseverity Set the lowest severity level to report (one of "error", "warning", "info") (default is "info") -e --exitcode Exit code to use if there are results with severity of "error". Conventionally, 0 is used for success and all non-zero codes for an error. (default is 2) --no-color Don't use colors in the output (default is false) Configuration File The kubeaudit config can be used for two things: Enabling only some auditors Specifying configuration for auditors Any configuration that can be specified using flags for the individual auditors can be represented using the config. The config has the following format: enabledAuditors:
# Auditors are enabled by default if they are not explicitly set to "false"
apparmor: false
asat: false
capabilities: true
deprecatedapis: true
hostns: true
image: true
limits: true
mounts: true
netpols: true
nonroot: true
privesc: true
privileged: true
rootfs: true
seccomp: true
auditors:
capabilities:
# add capabilities needed to the add list, so kubeaudit won't report errors
allowAddList: ['AUDIT_WRITE', 'CHOWN']
deprecatedapis:
# If no versions are specified and the'deprecatedapis' auditor is enabled, WARN
# results will be genereted for the resources defined with a deprecated API.
currentVersion: '1.22'
targetedVersion: '1.25'
image:
# If no image is specified and the 'image' auditor is enabled, WARN results
# will be generated for containers which use an ima ge without a tag
image: 'myimage:mytag'
limits:
# If no limits are specified and the 'limits' auditor is enabled, WARN results
# will be generated for containers which have no cpu or memory limits specified
cpu: '750m'
memory: '500m' For more details about each auditor, including a description of the auditor-specific configuration in the config, see the Auditor Docs (https://github.com/Shopify/kubeaudit#auditors). Note: The kubeaudit config is not the same as the kubeconfig file specified with the --kubeconfig flag, which refers to the Kubernetes config file (see Local Mode

___________________________
@hacking_Attack
@Hacking_Video

(https://github.com/Shopify/kubeaudit/blob/main/README.md#local-mode)). Also note that only the all and autofix commands support using a kubeaudit config. It will not work with other commands. Note: If flags are used in combination with the config file, flags will take precedence. Override Errors Security issues can be ignored for specific containers or pods by adding override labels. This means the auditor will produce info results instead of error results and the audit result name will have Allowed appended to it. The labels are documented in each auditor's documentation, but the general format for auditors that support overrides is as follows: An override label consists of a key and a value. The key is a combination of the override type (container or pod) and an override identifier which is unique to each auditor (see the docs (https://github.com/Shopify/kubeaudit#auditors) for the specific auditor). The key can take one of two forms depending on the override type: Container overrides, which override the auditor for that specific container, are formatted as follows: container.audit.kubernetes.io/[container name].[override identifier] Pod overrides, which override the auditor for all containers within the pod, are formatted as follows: audit.kubernetes.io/pod.[override identifier] If the value is set to a non-empty string, it will be displayed in the info result as the OverrideReason: $ kubeaudit asat -f "auditors/asat/fixtures/service-account-token-true-allowed.yml"

---------------- Results for ---------------

apiVersion: v1
kind: ReplicationController
metadata:
name: replicationcontroller
namespace: service-account-token-true-allowed

--------------------------------------------

-- [info] AutomountServiceAccountTokenTrueAndDefaultSAAllowed
Message: Audit result overridden: Default service account with token mounted. automountServiceAccountToken should be set to 'false' or a non-default service account should be used.
Metadata:
OverrideReason: SomeReason
As per Kubernetes spec, value must be 63 characters or less and must be empty or begin and end with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), underscores (_), dots (.), and alphanumerics between. Multiple override labels (for multiple auditors) can be added to the same resource. See the specific auditor docs (https://github.com/Shopify/kubeaudit#auditors) for the auditor you wish to override for examples. To learn more about labels, see https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ Contributing If you'd like to fix a bug, contribute a feature or just correct a typo, please feel free to do so as long as you follow our Code of Conduct (https://github.com/Shopify/kubeaudit/blob/master/CODE_OF_CONDUCT.md). Create your own fork! Get the source: go get github.com/Shopify/kubeaudit Go to the source: cd $GOPATH/src/github.com/Shopify/kubeaudit Add your forked repo as a fork: git remote add fork https://github.com/you-are-awesome/kubeaudit Create your feature branch: git checkout -b awesome-new-feature Install Kind (https://kind.sigs.k8s.io/#installation-and-usage) Run the tests to see everything is working as expected: make test (to run tests without Kind: USE_KIND=false make test) Commit your changes: git commit -am 'Adds awesome feature' Push to the branch: git push fork Sign the Contributor License Agreement (https://cla.shopify.com/) Submit a PR (All PR must be labeled with  (Bug fix), (New feature),(Documentation update), or(Breaking changes) ) ??? Profit Note that if you didn't sign the CLA before opening your PR, you can re-run the check by adding a comment to the PR that says "I've signed the CLA!"!

Download Kubeaudit (https://github.com/Shopify/kubeaudit)

___________________________
@hacking_Attack
@Hacking_Video

Authorization token leak from verify email endpoint
https://vengeance.medium.com/authorization-token-leak-from-verifying-email-endpoint-f28803476680?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

While testing a website I found that the verify email endpoint was leaking the authorization tokens of any verified users by just passing…Continue reading on Medium » (https://vengeance.medium.com/authorization-token-leak-from-verifying-email-endpoint-f28803476680?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Authorization token leak from verify email endpoint

While testing a website I found that the verify email endpoint was leaking the authorization tokens of any verified users by just passing…Continue reading on Medium »
Read more...

CRLF to Account takeover (chaining bugs)

Hi, everyoneContinue reading on Medium »
Read more...

Hacking on Medium
CRLF to Account takeover (chaining bugs)

https://cdn-images-1.medium.com/max/600/1*cmObGZE__peI9_yQYQTP0w.png
Hi, everyone

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

CRLF to Account takeover (chaining bugs)
https://medium.com/@moSec/crlf-to-account-takeover-chaining-bugs-21a25dfa1cdf?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Hi, everyoneContinue reading on Medium » (https://medium.com/@moSec/crlf-to-account-takeover-chaining-bugs-21a25dfa1cdf?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

https://b.thumbs.redditmedia.com/ft10xbq3hMql5JoWEE4Jw1yhDtejQrrG3jh3SkYz_xs.jpg Seeking focus groups/use cases: https://www.domaincodex.com

https://preview.redd.it/zh6yn260ryb91.png?width=1318&format=png&auto=webp&s=7fe201c6240f4a9ccdbc4f7f196e5b009a30096e

Search 390+million root domains (associative 25 data points). Mix and match any criteria/points, additional API access available via RapidAPI.

#data #osint #bigdata

All feedback welcomed: https://www.domaincodex.com/contact.php

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

First Bug Bounty from DOS: Taking the service down

Hello friends, This is Faique, a security researcher & an ethical hacker from India, and this is a journey to my first bug bounty.Continue reading on Medium »
Read more...

MS-Interloper: On the Subject of Malicious MSIs
https://www.reddit.com/r/redteamsec/comments/w0ky2p/msinterloper_on_the_subject_of_malicious_msis/

submitted by /u/dmchell (https://www.reddit.com/user/dmchell)
[link] (https://notes.huskyhacks.dev/notes/ms-interloper-on-the-subject-of-malicious-msis) [comments] (https://www.reddit.com/r/redteamsec/comments/w0ky2p/msinterloper_on_the_subject_of_malicious_msis/)

___________________________
@hacking_Attack
@Hacking_Video

First Bug Bounty from DOS: Taking the service down
https://medium.com/@faique/first-bug-bounty-from-dos-taking-the-service-down-30f9ad4e0246?source=rss------bug_bounty-5

Hello friends, This is Faique, a security researcher & an ethical hacker from India, and this is a journey to my first bug bounty.Continue reading on Medium » (https://medium.com/@faique/first-bug-bounty-from-dos-taking-the-service-down-30f9ad4e0246?source=rss------bug_bounty-5)

password reset No Rate Limiting
https://medium.com/@rishinikam/password-reset-no-rate-limiting-f46b93088ec0?source=rss------bug_bounty-5

hey gusy my name RISHI NIKAM i am Security Researcher and bug bounty hunterContinue reading on Medium » (https://medium.com/@rishinikam/password-reset-no-rate-limiting-f46b93088ec0?source=rss------bug_bounty-5)