e Content-Type header
* --useragentchrome/-uacchanges the User-Agent from WebCacheVulnerabilityScanner v{Version-Number}to Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36. While the same can be achieved with e.g. -sh "Mozilla/5.0 (Windows NT 10.0; Win64; x64) ..., this flag provides a quicker way. Examples

wcvs -u https://example.com -sc “PHPSESSID=123”
wcvs -u https://example.com -sc “file:/home/user/Documents/cookies.txt”
wcvs -u https://example.com -sh “Referer: localhost”
wcvs -u https://example.com -sh “file:/home/user/Documents/headers.txt”
wcvs -u https://example.com -sp “admin=true”
wcvs -u https://example.com -sp “file:/home/user/Documents/parameters.txt”
wcvs -u https://example.com -post -sb “admin=true”
wcvs -u https://example.com -post -sb “file:/home/user/Documents/body.txt”
wcvs -u https://example.com -post -sb “{}” -ct “application/json”
wcvs -u https://example.com -uac

Generate a JSON Report

A JSON report is generated and updated after each scanned URL if the flag --generatereport/-gris set. The report is written, just like a log file, into the same directory WCVS is executed from. In order to change the directory for all output files use --generatepath/-gp. If HTML special chars shall be encoded in the report, use --escapejson/-ej. Examples

wcvs -u https://example.com -gr
wcvs -u https://example.com -gr -ej
wcvs -u https://example.com -gr -gp /home/user/Documents
wcvs -u https://example.com -gr -gp /home/user/Documents -ej

Use a Proxy

To use a proxy, a CA certificate of the proxy in PEM format is needed. Burp Suite certificates are provided in DER format, for example. To convert them, the following command can be used: openssl x509 -inform DER -outform PEM -text -in cacert.der -out cacert.pem. The path to the certificate can be specified with --proxycertpath/-ppath. The default URL for the proxy is http://127.0.0.1:8080. In order to change it, use --proxyurl/-purl. Examples

wcvs -u https://example.com -ppath /home/user/Documents/cacert.pem
wcvs -u https://example.com -ppath /home/user/Documents/cacert.pem -purl http://127.0.0.1:8081

Throttle or Accelerate

The number of maximum allowed requests per second can be set with --reqrate/-rr. By default, this number is unrestricted. Contrary, the number of requests per second can be increased potentially, if --threads/-tis used to increase the number of concurrent threads WCVS utilizes. The default value is 20. Examples

wcvs -u https://example.com -rr 10
wcvs -u https://example.com -rr 1
wcvs -u https://example.com -rr 0.5
wcvs -u https://example.com -t 50

Further Flags

WCVS provides even more than the beforehand mentioned flags and options. --help/-hprovides a list of each flag, its meaning, and how to use it. Example

wcvs -h Download

___________________________
@hacking_Attack
@Hacking_Video

Kali Linux Tutorials
Mesh-Kridik : An Open-Source Security Checker That Performs Security Checks On A Kubernetes Cluster

Mesh-Kridik is an open-source security checker that performs various security checks on a Kubernetes cluster with istio service mesh and outputs a security report

The security checks tests are the full implementation of istio security best practices

The security checks performed on a Kubernetes cluster with istio service mesh and is leveraged by OPA (Open Policy Agent) to enforce security rules, and the output audit report includes: the root cause of the security issue and proposed remediation for the security issue.

Requirements

* Go 1.16+
* jq
* istio Installation

git clone https://github.com/chen-keinan/mesh-kridik
cd mesh-kridik
make build

* ote: mesh-kridik require root user to be executed Quick Start

Execute Mesh-Kridik without any flags , execute all tests

./mesh-kridik

Execute mesh-kridik with flags , execute test on demand

Usage: mesh-kridik [–version] [–help] []
Available commands are:
-r , –report : run security checks and generate remediation report
-i , –include: execute only specific security check, example -i=1.1
-e , –exclude: ignore specific security check, example -e=1.1,2.0

Execute tests and generate failure tests report and it remediation’s

./mesh-kridik -r

Istio Security Checks
NameDescriptionImpactMutual TLSIstio Mutual TLS proxies are configured in permissive mode by defaultproxies will accept both mutual TLS and plaintext trafficIstio Safer Authorization Policy PatternsUse ALLOW-with-positive-matching or DENY-with-negative-match patternsThese authorization policy patterns are safer because the worst result in the case of policy mismatch is an unexpected 403 rejection instead of an authorization policy bypass.path normalization in authorization policyThe enforcement point for authorization policies is the Envoy proxy instead of the usual resource access point in the backend applicationA mismatch can lead to either unexpected rejection or a policy bypassTLS origination for egress trafficUse of DestinationRule on service ServiceEntry for egress trafficNot using TLS origination for egress traffic to an external service will be send with plain/textProtocol detectionexplicitly declare the service protocolmiss detection may result in unexpected traffic behaviorCNI supportistio transparent traffic capturenot al net traffic will not be captureoverly broad hostsavoid overly broad hosts settings in Gatewaymay cause potential exposure of unexpected domainsRestrict Gateway creation privilegesrestrict creation of Gateway resources to trusted cluster administratorsmay cause creation of gateway by untrusted usersConfigure a limit on downstream connectionsUpdate global_downstream_max_connections in the config map according to the number of concurrent connections needed by individual gateway instances in your deployment. Once the limit is reached, Envoy will start rejecting tcp connectionsno limit on the number of downstream connections can cause exploited by a malicious actorConfigure third party service account tokensIt is recommended to configure 3rd party tokens Because the properties of the first party token are less securefirst party token properties are less secure and might cause authentication breachControl PlaneIstiod exposes a few unauthenticated plaintext ports for convenience by defaultexposes the XDS service port 15010 and debug port 8080 over unauthenticated plaintextData PlaneThe proxy exposes a variety of portsThe applications running in the same pod as the proxy have access; there is no trust boundary between the sidecar and applicationUnderstand traffic capture limitationsSecuring egress traffic by setting the meshConfig.outboundTrafficPolicy.modeexternal service access will not be controlled User Plugin Usage (via go plugins)

The Kube-kridik expose a hook[...]

___________________________
@hacking_Attack
@Hacking_Video

for user plugins Example :

* MeshSecurityCheckResultHook – this hook accepts k8s service mesh security checks results Compile user plugin

go build -buildmode=plugin -o=~//.so ~//.go

Copy plugin to folder (.kube-kridik folder is created on the 1st startup)

cp ~//.so ~/.kube-kridik/plugins/compile/.so Download

___________________________
@hacking_Attack
@Hacking_Video

Chain-Reactor - An Open Source Framework For Composing Executables That Simulate Adversary Behaviors And Techniques On Linux Endpoints

Chain Reactor is an open-source tool for testing detection and response coverage on Linux machines. The tool generates executables that simulate sequences of actions like process creation and network connection. Chain Reactor assumes no prior engineering experience; the tool consumes JSON, so customizing its behavior is as simple as editing a file. Get started For installation and usage instructions, see the Getting started page of the wiki. Learn more The Chain Reactor documentation is available as a wiki. For information about the philosophy and development of the atomic family of projects, visit our website at https://atomicredteam.io. Check the license for information regarding the distribution and modification of Chain Reactor. Download Chain-Reactor
Read more...

___________________________
@hacking_Attack
@Hacking_Video

Chain-Reactor - An Open Source Framework For Composing Executables That Simulate Adversary Behaviors And Techniques On Linux Endpoints

Chain Reactor is an open-source tool for testing detection and response coverage on Linux machines. The tool generates executables that simulate sequences of actions like process creation and network connection. Chain Reactor assumes no prior engineering experience; the tool consumes JSON, so customizing its behavior is as simple as editing a file. Get started For installation and usage instructions, see the Getting started page of the wiki. Learn more The Chain Reactor documentation is available as a wiki. For information about the philosophy and development of the atomic family of projects, visit our website at https://atomicredteam.io. Check the license for information regarding the distribution and modification of Chain Reactor. Download Chain-Reactor
Read more...

Chain-Reactor - An Open Source Framework For Composing Executables That Simulate Adversary Behaviors And Techniques On Linux Endpoints
http://www.kitploit.com/2022/02/chain-reactor-open-source-framework-for.html

___________________________
@hacking_Attack
@Hacking_Video

Chain Reactor is an open-source tool for testing (https://www.kitploit.com/search/label/Testing) detection and response coverage on Linux (https://www.kitploit.com/search/label/Linux) machines. The tool generates executables that simulate sequences of actions like process creation and network connection. Chain Reactor assumes no prior engineering experience; the tool consumes JSON, so customizing its behavior is as simple as editing a file.
Get started For installation and usage instructions, see the Getting started (https://github.com/redcanaryco/chain-reactor/wiki/Getting-started) page of the wiki. Learn more The Chain Reactor documentation is available as a wiki (https://github.com/redcanaryco/chain-reactor/wiki/). For information about the philosophy and development of the atomic family of projects, visit our website (https://www.kitploit.com/search/label/Website) at https://atomicredteam.io (https://atomicredteam.io/). Check the license (https://github.com/redcanaryco/chain-reactor/blob/master/LICENSE) for information regarding the distribution and modification of Chain Reactor.

Download Chain-Reactor (https://github.com/redcanaryco/chain-reactor)

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Security Explained: Regression Testing

https://cdn-images-1.medium.com/max/1920/0*5sq06KgLk1kUtyMg.jpg
There’s an element after penetration testing, regardless of which type of testing you choose, that we see often forgotten or neglected.

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
Chain-Reactor - An Open Source Framework For Composing Executables That Simulate Adversary Behaviors And Techniques On Linux Endpoints

http://4.bp.blogspot.com/-pjuemu0xLSI/Yd0gLAd4qoI/AAAAAAAA8o4/-0nl-C_vBCU7a851iAfWqqQ9B7sHYNXAQCK4BGAYYCw/w640-h378/chain-reactor_1_logo-744472.png
Chain Reactor is an open-source tool for testing detection and response coverage on Linux machines. The tool generates executables that simulate sequences of actions like process creation and network connection. Chain Reactor assumes no prior engineering experience; the tool consumes JSON, so customizing its behavior is as simple as editing a file.
Get started

For installation and usage instructions, see the Getting started page of the wiki.

Learn more

The Chain Reactor documentation is available as a wiki.

For information about the philosophy and development of the atomic family of projects, visit our website at https://atomicredteam.io.

Check the license for information regarding the distribution and modification of Chain Reactor.
Download Chain-Reactor

___________________________
@hacking_Attack
@Hacking_Video

rDEX Bug Bounty Recap
https://medium.com/stafi/rdex-bug-bounty-recap-d3e2aab48840?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

OverviewContinue reading on StaFi » (https://medium.com/stafi/rdex-bug-bounty-recap-d3e2aab48840?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

SQLi: next level

you may have seen some SQL injections that exploiting them are not as straightforward as what you see in the ethical hacking courses. like…Continue reading on Medium »
Read more...

SQLi: next level

you may have seen some SQL injections that exploiting them are not as straightforward as what you see in the ethical hacking courses. like…Continue reading on Medium »
Read more...

SQLi: next level
https://medium.com/@Rend_/sqli-next-level-5b1145b83c79?source=rss------bug_bounty-5

you may have seen some SQL injections that exploiting them are not as straightforward as what you see in the ethical hacking courses. like…Continue reading on Medium » (https://medium.com/@Rend_/sqli-next-level-5b1145b83c79?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

The most underrated tool in bug bounty. (and the filthiest one liner possible)
https://medium.com/@Sm9l/the-most-underrated-tool-in-bug-bounty-and-the-filthiest-one-liner-possible-cab14ef7faeb?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

One liner tool chains for bug bounty, dependent on one vital tool.Continue reading on Medium » (https://medium.com/@Sm9l/the-most-underrated-tool-in-bug-bounty-and-the-filthiest-one-liner-possible-cab14ef7faeb?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video