GitLab Watchman – Audit Gitlab For Sensitive Data & Credentials

Last updated: February 3, 2021 | 1,163 views 0

GitLab Watchman is an application that uses the GitLab API to audit GitLab for sensitive data and credentials exposed internally – this includes code, commits, wiki pages and more.

GitLab Watchman searches GitLab for internally shared projects and looks at:

Code
Commits
Wiki pages
Issues
Merge requests
Milestones

For the following data:

GCP keys and service account files
AWS keys
Azure keys and service account files
Google API keys
Slack API tokens & webhooks
Private keys (SSH, PGP, any other misc private key)
Exposed tokens (Bearer tokens, access tokens, client_secret etc.)
S3 config files
Passwords in plaintext
CICD variables exposed publicly
and more

Using GitLab Watchman to Audit Gitlab For Sensitive Data

GitLab Watchman will be installed as a global command, use as follows:

usage: gitlab-watchman [-h] --timeframe {d,w,m,a} --output
                   {file,stdout,stream} [--version] [--all] [--blobs]
                   [--commits] [--wiki-blobs] [--issues] [--merge-requests]
                   [--milestones] [--comments]

Monitoring GitLab for sensitive data shared publicly

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --all                 Find everything
  --blobs               Search code blobs
  --commits             Search commits
  --wiki-blobs          Search wiki blobs
  --issues              Search issues
  --merge-requests      Search merge requests
  --milestones          Search milestones
  --comments            Search comments

required arguments:
  --timeframe {d,w,m,a}
                        How far back to search: d = 24 hours w = 7 days, m =
                        30 days, a = all time
  --output {file,stdout,stream}
                        Where to send results

usage: gitlab-watchman [-h] --timeframe {d,w,m,a} --output

{file,stdout,stream} [--version] [--all] [--blobs]

[--commits] [--wiki-blobs] [--issues] [--merge-requests]

[--milestones] [--comments]

Monitoring GitLab for sensitive data shared publicly

optional arguments:

-h, --help show this help message and exit

--version show program's version number and exit

--all Find everything

--blobs Search code blobs

--commits Search commits

--wiki-blobs Search wiki blobs

--issues Search issues

--merge-requests Search merge requests

--milestones Search milestones

--comments Search comments

required arguments:

--timeframe {d,w,m,a}

How far back to search: d = 24 hours w = 7 days, m =

30 days, a = all time

--output {file,stdout,stream}

Where to send results

You can run GitLab Watchman to look for everything, and output to default Stdout:

gitlab-watchman --timeframe a --all

1	gitlab-watchman --timeframe a --all

Or arguments can be grouped together to search more granularly. This will look for commits and milestones for the last 30 days, and output the results to a TCP stream:

gitlab-watchman --timeframe m --commits --milestones --output stream

1	gitlab-watchman --timeframe m --commits --milestones --output stream

Logging in GitLab Watchman to Audit Gitlab For Sensitive Data

GitLab Watchman gives the following logging options:

Log file
Stdout
TCP stream

Results are output in JSON format, perfect for ingesting into a SIEM or other log analysis platform.

For file and TCP stream logging, configuration options need to be passed via .conf file or environment variable. See the file docs/logging.md for instructions on how to set it up.

If no logging option is given, GitLab Watchman defaults to Stdout logging.

You can download Gitlab Watchman here:

gitlab-watchman-1.4.0.tar.gz

Or read more here.

Topic: Countermeasures

GKE Auditor – Detect Google Kubernetes Engine Misconfigurations

Last updated: January 1, 2021 | 1,382 views 0

GKE Auditor is a Java-based tool to detect Google Kubernetes Engine misconfigurations, it aims to help security and development teams streamline the configuration process and save time looking for generic bugs and vulnerabilities.

The tool consists of individual modules called Detectors, each scanning for a specific vulnerability.

Installing and Using GKE Auditor to Detect Google Kubernetes Engine Misconfigurations

Installation

git clone https://github.com/google/gke-auditor
cd ./gke-auditor/
./build.sh

git clone https://github.com/google/gke-auditor

cd ./gke-auditor/

./build.sh

Usage

The tool has to be built by running the build.sh script first.

Once the tool is built, it can be run using the auditor.sh script, using the following options:

 ./auditor.sh [-a] [-ast] [-c] [-d] [-h] [-i <arg>] [-p <arg>] [-q]
       [-r <arg>]
 -a,--all          Run all detectors.
 -ast,--assets     Run all detectors for each individual asset.
 -c,--color        Turns on tool output coloring.
 -d,--defaults     Runs detectors including Kubernetes default assets.
                   Disabled by default.
 -h,--help         Print help information.
 -i,--iso <arg>    Run Node Isolation detectors.
                   To run all detectors, omit the argument list.
                   To specify individual detectors to run, give a list of
                   indices:
                   1. NODE_SELECTOR_POD_REJECTED
                   2. NODE_TAINTS_POD_REJECTED
                   3. NODE_AFFINITY_POD_REJECTED
 -p,--psp <arg>    Run PSP (Pod Security Policy) detectors.
                   To run all detectors, omit the argument list.
                   To specify individual detectors to run, give a list of
                   indices:
                   1. PRIVILEGED_CONTAINERS
                   2. CONTAINERS_SHARING_HOST_PROCESS_ID_NAMESPACE
                   3. CONTAINERS_SHARING_HOST_IPC
                   4. CONTAINER_SHARING_HOST_NETWORK_NAMESPACE
                   5. CONTAINERS_ALLOW_PRIVILEGE_ESCALATION
                   6. ROOT_CONTAINERS_ADMISSION
                   7. CONTAINERS_NET_RAW_CAPABILITY
                   8. CONTAINERS_ADDED_CAPABILITIES
                   9. CONTAINERS_CAPABILITIES_ASSIGNED
 -q,--quiet        Prints out only misconfigurations, without additional
                   detector info. Disabled by default.
 -r,--rbac <arg>   Run RBAC (Role Based Access Control) detectors.
                   To run all detectors, omit the argument list.
                   To specify individual detectors to run, give a list of
                   indices:
                   1. CLUSTER_ADMIN_ROLE_USED
                   2. SECRET_ACCESS_ALLOWED
                   3. WILDCARD_USED
                   4. CREATE_PODS_ALLOWED
                   5. AUTOMOUNT_SERVICE_ACCOUNT_TOKEN_ENABLED
                   6. ESCALATING_RESOURCES_REPORT

./auditor.sh [-a] [-ast] [-c] [-d] [-h] [-i <arg>] [-p <arg>] [-q]

[-r <arg>]

-a,--all Run all detectors.

-ast,--assets Run all detectors for each individual asset.

-c,--color Turns on tool output coloring.

-d,--defaults Runs detectors including Kubernetes default assets.

Disabled by default.

-h,--help Print help information.

-i,--iso <arg> Run Node Isolation detectors.

To run all detectors, omit the argument list.

To specify individual detectors to run, give a list of

indices:

1. NODE_SELECTOR_POD_REJECTED

2. NODE_TAINTS_POD_REJECTED

3. NODE_AFFINITY_POD_REJECTED

-p,--psp <arg> Run PSP (Pod Security Policy) detectors.

To run all detectors, omit the argument list.

To specify individual detectors to run, give a list of

indices:

1. PRIVILEGED_CONTAINERS

2. CONTAINERS_SHARING_HOST_PROCESS_ID_NAMESPACE

3. CONTAINERS_SHARING_HOST_IPC

4. CONTAINER_SHARING_HOST_NETWORK_NAMESPACE

5. CONTAINERS_ALLOW_PRIVILEGE_ESCALATION

6. ROOT_CONTAINERS_ADMISSION

7. CONTAINERS_NET_RAW_CAPABILITY

8. CONTAINERS_ADDED_CAPABILITIES

9. CONTAINERS_CAPABILITIES_ASSIGNED

-q,--quiet Prints out only misconfigurations, without additional

detector info. Disabled by default.

-r,--rbac <arg> Run RBAC (Role Based Access Control) detectors.

To run all detectors, omit the argument list.

To specify individual detectors to run, give a list of

indices:

1. CLUSTER_ADMIN_ROLE_USED

2. SECRET_ACCESS_ALLOWED

3. WILDCARD_USED

4. CREATE_PODS_ALLOWED

5. AUTOMOUNT_SERVICE_ACCOUNT_TOKEN_ENABLED

6. ESCALATING_RESOURCES_REPORT

General Detector Output Format for GKE Auditor

Detector: Detector name

Explanation: A short explanation of the concept that is being checked. Describes how and why the concept be a security issue. Often includes links to the documentation for more information.

Remediation: Steps to take in order to review the problem and resolve the vulnerability.

Useful links: Links to the documentation or other resources where the customer can learn about the issues at hand.

Level: one of [VULNERABILITY, WARNING]. VULNERABILITY implies security recommendations are not being followed, whereas a WARNING is informational and implies a potential vulnerability could exist.

Severity: one of [LOW, MEDIUM, HIGH]. Indicator of the seriousness of detected issues.

Vulnerable assets: List of assets that have the above-described vulnerability.

You can download GKE Auditor here:

gke-auditor-master.zip

Or read more here.

Topic: Countermeasures

zANTI – Android Wireless Hacking Tool Free Download

Last updated: December 7, 2020 | 9,735 views

zANTI is an Android Wireless Hacking Tool that functions as a mobile penetration testing toolkit that lets you assess the risk level of a network using your mobile device for free download.

This easy to use mobile toolkit enables IT Security Administrators to simulate an advanced attacker to identify the malicious techniques they use in the wild to compromise the corporate network.

Features of zANTI Android Wireless Hacking Tool

This network auditor comes along with a rather simple interface compared to other solutions and running its tasks is pretty straightforward. These are its main features:

Scan
Conduct network scans, in different intensity levels in order to identify connected devices, their properties and their vulnerabilities.

Diagnose

Enable Security Officers to easily evaluate an organization’s network and automatically diagnose vulnerabilities within mobile devices or web sites using a host of penetration tests including, man-in-the-Middle (MITM), password cracking and Metasploit.

Report

Highlight security gaps in your existing network and mobile defences and report the results with advanced cloud-based reporting through zConsole. zANTI mirrors the methods a cyber-attacker can use to identify security holes within your network. Dash-board reporting enables businesses to see the risks and take appropriate corrective actions to fix critical security issues.

Installing zANTI Android Wireless Hacking Tool

Minimum operating system requirements: Android 4.0.
The installation of the app by means of the APK file requires the activation of the “Unknown sources” option within Settings>Applications.

You can download zANTI here – the password is darknet123! –

zAnti3.19.apk.zip

Or read more here.

Topic: Hacking Tools

HELK – Open Source Threat Hunting Platform

Last updated: November 6, 2020 | 5,247 views

The Hunting ELK or simply the HELK is an Open-Source Threat Hunting Platform with advanced analytics capabilities such as SQL declarative language, graphing, structured streaming, and even machine learning via Jupyter notebooks and Apache Spark over an ELK stack.

This project was developed primarily for research, but due to its flexible design and core components, it can be deployed in larger environments with the right configurations and scalable infrastructure.

Goals of HELK Open Source Threat Hunting Platform

Provide an open-source hunting platform to the community and share the basics of Threat Hunting.
Expedite the time it takes to deploy a hunting platform.
Improve the testing and development of hunting use cases in an easier and more affordable way.
Enable Data Science capabilities while analyzing data via Apache Spark, GraphFrames & Jupyter Notebooks.

Installing HELK Open Source Threat Hunting Platform

You can start playing with the HELK in a few steps:

Step 1, download:

    git clone https://github.com/Cyb3rWard0g/HELK.git

1	git clone https://github.com/Cyb3rWard0g/HELK.git

Step 2, install:

    cd HELK/
    sudo ./helk_install.sh

1 2	cd HELK/ sudo ./helk_install.sh

You can download HELK here:

HELK-v0.1.7-alpha03042019.zip

Or read more here.

Topic: Hacking Tools

Fuzzilli – JavaScript Engine Fuzzing Library

Last updated: October 22, 2020 | 1,783 views

Fuzzilii is a JavaScript engine fuzzing library, it’s a coverage-guided fuzzer for dynamic language interpreters based on a custom intermediate language (“FuzzIL”) which can be mutated and translated to JavaScript. When fuzzing for core interpreter bugs, e.g. in JIT compilers, semantic correctness of generated programs becomes a concern. This is in contrast to most other […]

Topic: Exploits/Vulnerabilities

1 2 … 349 Next →

Navigation

Darknet

GitLab Watchman – Audit Gitlab For Sensitive Data & Credentials

Using GitLab Watchman to Audit Gitlab For Sensitive Data

Logging in GitLab Watchman to Audit Gitlab For Sensitive Data

GKE Auditor – Detect Google Kubernetes Engine Misconfigurations

Installing and Using GKE Auditor to Detect Google Kubernetes Engine Misconfigurations

Installation

Usage

General Detector Output Format for GKE Auditor

zANTI – Android Wireless Hacking Tool Free Download

Features of zANTI Android Wireless Hacking Tool

Installing zANTI Android Wireless Hacking Tool

HELK – Open Source Threat Hunting Platform

Goals of HELK Open Source Threat Hunting Platform

Installing HELK Open Source Threat Hunting Platform

Fuzzilli – JavaScript Engine Fuzzing Library