ne 8 and work at your own k8s setup),
* docker,
* helm Install from here,
* kubectl Install from here,
* jq Install from here,
* vault Install from here,
* grep, Cat, and Sed

Run ./k8s-vault-minkube-start.sh, when the script is done, then the challenges will wait for you at http://localhost:8080 . This will allow you to run challenges 1-8, 12-15.

When you stopped the k8s-vault-minikube-start.shscript and want to resume the port forward run: k8s-vault-minikube-resume.sh. This is because if you run the start script again it will replace the secret in the vault and not update the secret-challenge application with the new secret. Cloud ChallengesCan be used for challenges 1-16

READ THIS: Given that the exercises below contain IAM privilege escalation exercises, never run this on an account which is related to your production environment or can influence your account-over-arching resources. Running WrongSecrets in AWSFollow the steps in the README in the AWS subfolder. Running WrongSecrets in GCPFollow the steps in the README in the GCP subfolder. Running WrongSecrets in AzureFollow the steps in the README in the Azure subfolder. Running Challenge15 in your own cloud onlyWhen you want to include your own Canarytokens for your cloud-deployment, do the following:

1. Fork the project.
2. Make sure you use the GCP ingress or AWS ingress scripts to generate an ingress for your project.
3. Go to canarytokens.org and select AWS Keys, in the webHook URL field add .
4. Encrypt the received credentials so that Challenge15 can decrypt them again.
5. Commit the unencrypted and encrypted materials to Git and then commit again without the decrypted materials.
6. Adapt the hints of Challenge 15 in your fork to point to your fork.
7. Create a container and push it to your registry
8. Override the K8s definition files for either AWS or GCP. Do you want to play without guidance?Each challenge has a Show hintsbutton and a What's wrong?button. These buttons help to simplify the challenges and give explanation to the reader. Though, the explanations can spoil the fun if you want to do this as a hacking exercise. Therefore, you can manipulate them by overriding the following settings in your env:

* hints_enabled=falsewill turn off the Show hintsbutton.
* reason_enabled=falsewill turn of the What's wrong?explanation button. Special thanks & ContributorsLeaders:

* Ben de Haan @bendehaan
* Jeroen willemsen @commjoen

Top contributors:

* Nanne Baars @nbaars
* Marcin Nowak @MarcinNowak-codes
* Tibor Hercz @tiborhercz
* Filip Chyla @fchyla
* Dmitry Litosh @Dlitosh
* Josh Grossman @tghosth
* Spyros @northdpole
* Mike Woudenberg @mikewoudenberg
* Ruben Kruiver @RubenAtBinx
* Finn @f3rn0s
* Joss Sparkes @remakingeden

Testers:

* Dave van Stein @davevs
* Marcin Nowak @MarcinNowak-codes
* Marc Chang Sing Pang @mchangsp

Special mentions for helping out:

* Madhu Akula @madhuakula
* Björn Kimminich @bkimminich
* Avinash Pancham @avinashpancham Help WantedYou can help us by the following methods:

* Star us
* Share this app with others
* Of course, we can always use your help to get more flavors of "wrongly" configured secrets in to spread awareness! We would love to get some help with other cloudproiders, like Alibabaor Tencent cloud for instance. Do you miss something else than a cloud provider as an example? File an issue or create a PR! See our guide on contributing for more details. Contributors will be listed in releases, in the "Special thanks & Contributors"-section, and the web-app. Use OWASP WrongSecrets as a secret detection benchmarkAs tons of secret detection tools are coming up for both Docker and Git, we are creating a Benchmark testbed for it. Want to know if your tool detects [...]

___________________________
@hacking_Attack
@Hacking_Video

everything? We will keep track of the embedded secrets in this issue and have a branch in which we put additional secrets for your tool to detect. The branch will contain a Docker container generation script using which you can eventually test your container secret scanning. Notes on developmentFor development on local machine use the localprofile ./mvnw spring-boot:run -Dspring-boot.run.profiles=localIf you want to test against vault without K8s: start vault locally with export VAULT_ADDR='http://127.0.0.1:8200'
export VAULT_API_ADDR='http://127.0.0.1:8200'
vault server -devand in your next terminal, do (with the token from the previous commands): export VAULT_ADDR='http://127.0.0.1:8200'
export VAULT_TOKEN='Now use the local-vaultprofile to do your development. ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,local-vaultIf you want to dev without a Vault instance, use additionally the without-vaultprofile to do your development: ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,without-vaultWant to push a container? See .github/scripts/docker-create-and-push.shfor a script that generates and pushes all containers. Do not forget to rebuild the app before composing the container Dependency managementWe have CycloneDX and OWASP Dependency-check integrated to check dependencies for vulnerabilities. You can use the OWASP Dependency-checker by calling mvn dependency-check:aggregateand mvn cyclonedx:makeBomto use CycloneDX to create an SBOM. Automatic reload during developmentTo make changes made load faster we added spring-dev-toolsto the Maven project. To enable this in IntelliJ automatically, make sure:

* Under Compiler -> Automatically build project is enabled, and
* Under Advanced settings -> Allow auto-make to start even if developed application is currently running.

You can also manually invoke: Build -> Recompile the file you just changed, this will also force reloading of the application. How to add a ChallengeFollow the steps below on adding a challenge:

1. First make sure that you have an Issue reported for which a challenge is really wanted.
2. Add the new challenge in the org.owasp.wrongsecrets.challengesfolder. Make sure you add an explanation in src/main/resources/explanationsand refer to it from your new Challenge class.
3. Add a unit and integration test to show that your challenge is working.
4. Don't forget to add @Orderannotation to your challenge ;-).

If you want to move existing cloud challenges to another cloud: extend Challenge classes in the org.owasp.wrongsecrets.challenges.cloudpackage and make sure you add the required Terraform in a folder with the separate cloud identified. Make sure that the environment is added to org.owasp.wrongsecrets.RuntimeEnvironment. Collaborate with the others at the project to get your container running so you can test at the cloud account. Download Wrongsecrets

___________________________
@hacking_Attack
@Hacking_Video

Wrongsecrets - Examples With How To Not Use Secrets
http://www.kitploit.com/2022/05/wrongsecrets-examples-with-how-to-not.html

___________________________
@hacking_Attack
@Hacking_Video

Welcome to the OWASP WrongSecrets p0wnable app. With this app, we have packed various ways of how to not store your secrets. These can help you to realize whether your secret management (https://www.kitploit.com/search/label/Secret%20Management) is ok. The challenge is to find all the different secrets by means of various tools and techniques. Can you solve all the 16 challenges? 
Support Need support? Contact us via OWASP Slack (https://owasp.slack.com/archives/C02KQ7D9XHR) for which you sign up here (https://owasp.org/slack/invite), file a PR (https://github.com/commjoen/wrongsecrets/pulls), file an issue (https://github.com/commjoen/wrongsecrets/issues) , or use discussions (https://github.com/commjoen/wrongsecrets/discussions). Please note that this is an OWASP volunteer based project, so it might take a little while before we respond. Basic docker exercises Can be used for challenges 1-4, 8, 12-15 For the basic docker exercises you currently require: Docker Install from here (https://docs.docker.com/get-docker/) Some Browser that can render HTML You can install it by doing: docker run -p 8080:8080 jeroenwillemsen/wrongsecrets:1.4.0-no-vault Now you can try to find the secrets by means of solving the challenge offered at: localhost:8080/challenge/1 (http://localhost:8080/challenge/1) localhost:8080/challenge/2 (http://localhost:8080/challenge/2) localhost:8080/challenge/3 (http://localhost:8080/challenge/3) localhost:8080/challenge/4 (http://localhost:8080/challenge/4) localhost:8080/challenge/8 (http://localhost:8080/challenge/8) localhost:8080/challenge/12 (http://localhost:8080/challenge/12) localhost:8080/challenge/13 (http://localhost:8080/challenge/13) localhost:8080/challenge/14 (http://localhost:8080/challenge/14) localhost:8080/challenge/15 (http://localhost:8080/challenge/15) localhost:8080/challenge/16 (http://localhost:8080/challenge/16) Note that these challenges are still very basic, and so are their explanations. Feel free to file a PR to make them look better ;-). Running these on Heroku You can test them out at https://wrongsecrets.herokuapp.com/ as well! But please understand that we have NO guarantees that this works. Given we run in Heroku free-tier, please do not fuzz and/or try to bring it down: you would be spoiling it for others that want to testdrive it. Deploying the app under your own heroku account Sign up to Heroku (https://signup.heroku.com/) and log in to your account (https://id.heroku.com/login) Click the button below and follow the instructions Basic K8s exercise Can be used for challenges 1-6, 8, 12-16 Minikube based Make sure you have the following installed: Docker Install from here (https://docs.docker.com/get-docker/) Minikube Install from here (https://minikube.sigs.k8s.io/docs/start/) The K8S setup currently is based on using Minikube for local fun: minikube start
kubectl apply -f k8s/secrets-config.yml
kubectl apply -f k8s/secrets-secret.yml
kubectl apply -f k8s/secret-challenge-deployment.yml
while [[ $(kubectl get pods -l app=secret-challenge -o 'jsonpath={..status.conditions[?(@.type=="Ready")].status}') != "True" ]]; do echo "waiting for secret-challenge" && sleep 2; done
kubectl expose deployment secret-challenge --type=LoadBalancer --port=8080
minikube service secret-challenge now you can use the provided IP address and port to further play with the K8s variant (instead of localhost). localhost:8080/challenge/5 (http://localhost:8080/challenge/5) localhost:8080/challenge/6 (http://localhost:8080/challenge/6) k8s based Want to run vanilla on your own k8s? Use the commands below: kubectl apply -f k8s/secrets-config.yml
kubectl apply -f k8s/secrets-secret.yml
kubectl apply -f k8s/secret-challenge-deployment.yml

___________________________
@hacking_Attack
@Hacking_Video

while [[ $(kubectl get pods -l app=secret-challenge -o 'jsonpath={..status.conditions[?(@.type=="Ready")].status}') != "True" ]]; do echo "waiting for secret-challenge" && sleep 2; done
kubectl port-forward \
$(kubectl get pod -l app=secret-challenge -o jsonpath="{.items[0].metadata.name}") \
8080:8080 now you can use the provided IP address and port to further play with the K8s variant (instead of localhost). localhost:8080/challenge/5 (http://localhost:8080/challenge/5) localhost:8080/challenge/6 (http://localhost:8080/challenge/6) Vault exercises with minikube Can be used for challenges 1-8, 12-16 Make sure you have the following installed: minikube with docker (or comment out line 8 and work at your own k8s setup), docker, helm Install from here (https://helm.sh/docs/intro/install/), kubectl Install from here (https://kubernetes.io/docs/tasks/tools/), jq Install from here (https://stedolan.github.io/jq/download/), vault Install from here (https://www.vaultproject.io/downloads), grep, Cat, and Sed Run ./k8s-vault-minkube-start.sh, when the script is done, then the challenges will wait for you at http://localhost:8080 (http://localhost:8080/) . This will allow you to run challenges 1-8, 12-15. When you stopped the k8s-vault-minikube-start.sh script and want to resume the port forward (https://www.kitploit.com/search/label/Port%20Forward) run: k8s-vault-minikube-resume.sh. This is because if you run the start script again it will replace the secret in the vault and not update the secret-challenge application with the new secret. Cloud Challenges Can be used for challenges 1-16 READ THIS: Given that the exercises below contain IAM privilege escalation (https://www.kitploit.com/search/label/Privilege%20Escalation) exercises, never run this on an account which is related to your production environment or can influence your account-over-arching resources. Running WrongSecrets in AWS Follow the steps in the README in the AWS subfolder (https://github.com/commjoen/wrongsecrets/blob/master/aws/README.md). Running WrongSecrets in GCP Follow the steps in the README in the GCP subfolder (https://github.com/commjoen/wrongsecrets/blob/master/gcp/README.md). Running WrongSecrets in Azure Follow the steps in the README in the Azure subfolder (https://github.com/commjoen/wrongsecrets/blob/master/azure/README.md). Running Challenge15 in your own cloud only When you want to include your own Canarytokens for your cloud-deployment, do the following: Fork the project. Make sure you use the GCP ingress (https://github.com/commjoen/wrongsecrets/blob/master/gcp/k8s-vault-gcp-ingress-start.sh) or AWS ingress (https://github.com/commjoen/wrongsecrets/blob/master/aws/k8s-aws-alb-script.sh) scripts to generate an ingress for your project. Go to canarytokens.org (https://canarytokens.org/generate) and select AWS Keys, in the webHook URL field add /canaries/tokencallback. Encrypt the received credentials (https://www.kitploit.com/search/label/Credentials) so that Challenge15 (https://github.com/commjoen/wrongsecrets/blob/master/src/main/java/org/owasp/wrongsecrets/challenges/docker/Challenge15.java) can decrypt them again. Commit the unencrypted and encrypted materials to Git and then commit again without the decrypted materials. Adapt the hints of Challenge 15 in your fork to point to your fork. Create a container and push it to your registry Override the K8s definition files for either AWS (https://github.com/commjoen/wrongsecrets/blob/master/aws/k8s/secret-challenge-vault-deployment.yml) or GCP (https://github.com/commjoen/wrongsecrets/blob/master/gcp/k8s/secret-challenge-vault-deployment.yml.tpl). Do you want to play without guidance? Each challenge has a Show hints button and a What's wrong? button. These buttons help to simplify the challenges and give explanation to the reader. Though, the explanations can spoil the fun if you want to do this as a hacking exercise.

___________________________
@hacking_Attack
@Hacking_Video

Therefore, you can manipulate them by overriding the following settings in your env: hints_enabled=false will turn off the Show hints button. reason_enabled=false will turn of the What's wrong? explanation button. Special thanks & Contributors Leaders: Ben de Haan @bendehaan (https://github.com/bendehaan) Jeroen willemsen @commjoen (https://github.com/commjoen) Top contributors: Nanne Baars @nbaars (https://github.com/nbaars) Marcin Nowak @MarcinNowak-codes (https://github.com/MarcinNowak-codes) Tibor Hercz @tiborhercz (https://github.com/tiborhercz) Filip Chyla @fchyla (https://github.com/fchyla) Dmitry Litosh @Dlitosh (https://github.com/Dlitosh) Josh Grossman @tghosth (https://github.com/tghosth) Spyros @northdpole (https://github.com/northdpole) Mike Woudenberg @mikewoudenberg (https://github.com/mikewoudenberg) Ruben Kruiver @RubenAtBinx (https://github.com/RubenAtBinx) Finn @f3rn0s (https://github.com/f3rn0s) Joss Sparkes @remakingeden (https://github.com/remakingeden) Testers: Dave van Stein @davevs (https://github.com/davevs) Marcin Nowak @MarcinNowak-codes (https://github.com/MarcinNowak-codes) Marc Chang Sing Pang @mchangsp (https://github.com/mchangsp) Special mentions for helping out: Madhu Akula @madhuakula (https://github.com/madhuakula) Björn Kimminich @bkimminich (https://github.com/bkimminich) Avinash Pancham @avinashpancham (https://github.com/avinashpancham) Help Wanted You can help us by the following methods: Star us Share this app with others Of course, we can always use your help to get more flavors (https://github.com/commjoen/wrongsecrets/issues/37) of "wrongly" configured secrets in to spread awareness! We would love to get some help with other cloudproiders, like Alibabaor Tencent cloud for instance. Do you miss something else than a cloud provider as an example? File an issue or create a PR! See our guide on contributing for more details (https://github.com/commjoen/wrongsecrets/blob/master/CONTRIBUTING.md). Contributors will be listed in releases, in the "Special thanks & Contributors"-section, and the web-app. Use OWASP WrongSecrets as a secret detection benchmark As tons of secret detection tools are coming up for both Docker and Git, we are creating a Benchmark testbed for it. Want to know if your tool detects everything? We will keep track of the embedded secrets in this issue (https://github.com/commjoen/wrongsecrets/issues/201) and have a branch (https://github.com/commjoen/wrongsecrets/tree/experiment-bed) in which we put additional secrets for your tool to detect. The branch will contain a Docker container generation script using which you can eventually test your container secret scanning. Notes on development For development on local machine use the local profile ./mvnw spring-boot:run -Dspring-boot.run.profiles=local If you want to test against vault without K8s: start vault locally with export VAULT_ADDR='http://127.0.0.1:8200'
export VAULT_API_ADDR='http://127.0.0.1:8200'
vault server -dev and in your next terminal, do (with the token from the previous commands): ' vault token create -id="00000000-0000-0000-0000-000000000000" -policy="root" vault kv put secret/secret-challenge vaultpassword.password="$(openssl rand -base64 16)"">export VAULT_ADDR='http://127.0.0.1:8200'
export VAULT_TOKEN=''
vault token create -id="00000000-0000-0000-0000-000000000000" -policy="root"
vault kv put secret/secret-challenge vaultpassword.password="$(openssl rand -base64 16)" Now use the local-vault profile to do your development. ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,local-vault If you want to dev without a Vault instance, use additionally the without-vault profile to do your development: ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,without-vault Want to push a container? See .github/scripts/docker-create-and-push.sh for a script that generates and pushes all containers. Do not forget to rebuild the

___________________________
@hacking_Attack
@Hacking_Video

app before composing the container Dependency management We have CycloneDX and OWASP Dependency-check integrated to check dependencies for vulnerabilities. You can use the OWASP Dependency-checker by calling mvn dependency-check:aggregate and mvn cyclonedx:makeBom to use CycloneDX to create an SBOM. Automatic reload during development To make changes made load faster we added spring-dev-tools to the Maven project. To enable this in IntelliJ automatically, make sure: Under Compiler -> Automatically build project is enabled, and Under Advanced settings -> Allow auto-make to start even if developed application is currently running. You can also manually invoke: Build -> Recompile the file you just changed, this will also force reloading of the application. How to add a Challenge Follow the steps below on adding a challenge: First make sure that you have an Issue (https://github.com/commjoen/wrongsecrets/issues) reported for which a challenge is really wanted. Add the new challenge in the org.owasp.wrongsecrets.challenges folder. Make sure you add an explanation in src/main/resources/explanations and refer to it from your new Challenge class. Add a unit and integration test to show that your challenge is working. Don't forget to add @Order annotation to your challenge ;-). If you want to move existing cloud challenges to another cloud: extend Challenge classes in the org.owasp.wrongsecrets.challenges.cloud package and make sure you add the required Terraform in a folder with the separate cloud identified. Make sure that the environment is added to org.owasp.wrongsecrets.RuntimeEnvironment. Collaborate with the others at the project to get your container running so you can test at the cloud account.

Download Wrongsecrets (https://github.com/commjoen/wrongsecrets)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Newbie wanting to get into password hacking

Love hacking in general and want to get into it. Mostly interested right now in just password hacking like maybe a login to a computer or just an account online. Not using for malicious intent or anything just find it interesting and want to know what would be good to learn!

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

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Revenge on a scammer

Ran into a scammer who is trying to extort me. I have their reddit account. Instagram account and Snapchat account, I was really hoping to get their physical location to put some fear into them, but if there is any way to get revenge on them I would really be interested. I can provide all the info I have.

submitted by /u/Titan-uranus
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Good to see you back. I have always loved your write ups. Simple and to the point. Keep it up

Continue reading on Medium »
Read more...

Good to see you back. I have always loved your write ups. Simple and to the point. Keep it up
https://medium.com/@secretcontrol2/good-to-see-you-back-i-have-always-loved-your-write-ups-simple-and-to-the-point-keep-it-up-5f1443c33b8b?source=rss------bug_bounty-5

Continue reading on Medium » (https://medium.com/@secretcontrol2/good-to-see-you-back-i-have-always-loved-your-write-ups-simple-and-to-the-point-keep-it-up-5f1443c33b8b?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

WordPress User Meta Lite / Pro 2.4.3 Suffers Path Traversal Exploit
https://skynettools.medium.com/wordpress-user-meta-lite-pro-2-4-3-suffers-path-traversal-exploit-9e6658192532?source=rss------bug_bounty-5

More @ https://skynettools.com 
Currently the WordPress Plugin User Meta 2.4.3, both Lite and Pro is vulnerable to a Path Traversal…Continue reading on Medium » (https://skynettools.medium.com/wordpress-user-meta-lite-pro-2-4-3-suffers-path-traversal-exploit-9e6658192532?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Dark Reading: Attacks/Breaches
ESET Launches NetProtect Suite of Advanced Cybersecurity Offerings for Telcos and ISPs

.

___________________________
@hacking_Attack
@Hacking_Video

WordPress User Meta Lite / Pro 2.4.3 Suffers Path Traversal Exploit

More @ https://skynettools.com  Currently the WordPress Plugin User Meta 2.4.3, both Lite and Pro is vulnerable to a Path Traversal…Continue reading on Medium »
Read more...

Hacking on Medium
Cyber Legion — Who are we?

https://cdn-images-1.medium.com/max/1024/0*mKeX5G9-gFDC9QL1.jpg
®Cyber Legion Ltd is a UK-based cybersecurity start-up that provides IT security testing services to various organizations around the…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
HackThisSite Basic Mission 6

https://cdn-images-1.medium.com/max/700/0*fVl2pbxIpmXNqCEa.jpg
Alright so time to dive down into the wonderful history of system admins creating encryption algorithms instead of using well established…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video