mirror of
https://github.com/HackTricks-wiki/hacktricks-cloud.git
synced 2026-01-24 18:24:40 -08:00
translate 2
This commit is contained in:
@@ -177,4 +177,3 @@ If they are used for example inside a a bash command, you could perform a comman
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -113,4 +113,3 @@ AUTH_ROLE_PUBLIC = 'Admin'
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -45,4 +45,3 @@ These are the default permissions per default role:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -390,4 +390,3 @@ You can also pass these as environment variables `ATLANTIS_WEB_BASIC_AUTH=true`
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -257,4 +257,3 @@ jobs:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -136,4 +136,3 @@ cloudflare-zero-trust-network.md
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -135,4 +135,3 @@ TODO
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -63,4 +63,3 @@ TODO
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -35,4 +35,3 @@ concourse-enumeration-and-attacks.md
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -40,4 +40,3 @@ In order to execute tasks concourse must have some workers. These workers **regi
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -444,4 +444,3 @@ Accept-Encoding: gzip.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -153,4 +153,3 @@ Check a YAML pipeline example that triggers on new commits to master in [https:/
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -140,4 +140,3 @@ If you are inside the server you can also **use the `gitea` binary** to access/m
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -105,4 +105,3 @@ Different protections can be applied to a branch (like to master):
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -246,4 +246,3 @@ For more info check [https://www.chainguard.dev/unchained/what-the-fork-imposter
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -583,4 +583,3 @@ The following tools are useful to find Github Action workflows and even find vul
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,4 +4,3 @@
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,4 +4,3 @@
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,4 +4,3 @@
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -58,4 +58,3 @@ And the latest one use a short sha-1 that is bruteforceable.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -257,4 +257,3 @@ Different protections can be applied to a branch (like to master):
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -414,4 +414,3 @@ println(hudson.util.Secret.decrypt("{...}"))
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -96,4 +96,3 @@ According to [**the docs**](https://www.jenkins.io/blog/2019/02/21/credentials-m
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -107,4 +107,3 @@ The example curl command provided demonstrates how to make a request to Jenkins
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -91,4 +91,3 @@ for (c in creds) {
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -41,4 +41,3 @@ If you can access the configuration file of some pipeline configured you could j
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -38,4 +38,3 @@ If you are not executing a reverse shell but a simple command you can **see the
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -65,4 +65,3 @@ msf> use exploit/multi/http/jenkins_script_console
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -116,4 +116,3 @@ okta-hardening.md
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -201,4 +201,3 @@ Here you can download Okta agents to sync Okta with other technologies.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -106,4 +106,3 @@ Check this interesting article about the top 10 CI/CD risks according to Cider:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -860,4 +860,3 @@ Granting excessive permissions to team members and external collaborators can le
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -165,4 +165,3 @@ It's possible to **store secrets** in supabase also which will be **accessible b
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -314,4 +314,3 @@ brew install terrascan
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -18,4 +18,3 @@ Github PRs are welcome explaining how to (ab)use those platforms from an attacke
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -67,4 +67,3 @@ If an attacker ends in an environment which uses **TravisCI enterprise** (more i
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -94,4 +94,3 @@ The amount of deployed TCI Worker and build environment OS images will determine
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -439,4 +439,3 @@ An **Access Group** in Vercel is a collection of projects and team members with
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user