Kali Linux Tutorials
SecureCodeBox : Automate A Bunch Of Security-Testing Tools Out Of The Box

secureCodeBox is a kubernetes based, modularized toolchain for continuous security scans of your software project. Its goal is to orchestrate and easily automate a bunch of security-testing tools out of the box. Purpose of this ProjectThe typical way to ensure application security is to hire a security specialist (aka penetration tester) at some point in your project to check the application for security bugs and vulnerabilities. Usually, this check is done at a later stage of the project and has two major drawbacks:

1. Nowadays, a lot of projects do continuous delivery, which means the developers deploy new versions multiple times each day. The penetration tester is only able to check a single snapshot, but some further commits could introduce new security issues. To ensure ongoing application security, the penetration tester should also continuously test the application. Unfortunately, such an approach is rarely financially feasible.
2. Due to a typically time boxed analysis, the penetration tester has to focus on trivial security issues (low-hanging fruit) and therefore will probably not address the serious, non-obvious ones.

With the secureCodeBox we provide a toolchain for continuous scanning of applications to find the low-hanging fruit issues early in the development process and free the resources of the penetration tester to concentrate on the major security issues.
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqudVeTv9c5jH7qrTERaoVPxex1LlOOtZx9qqX7AsmGM3nVz07aifVTlS-AKQ1te59W9-4XdG4o9_IzYWWlbA1rXqDockfDqlkOrUY7LGVhFDee1_ADCzanDasD5nqUIpLBED_45iQhe8WSmydFmacClAxwXEWq_8Ccjp2NVKIGOtUqFNmVAjQCxZd/s2525/macbook_kibana.jpg
The purpose of secureCodeBox is not to replace the penetration testers or make them obsolete. We strongly recommend to run extensive tests by experienced penetration testers on all your applications.

Important note: The secureCodeBox is no simple one-button-click-solution! You must have a deep understanding of security and how to configure the scanners. Furthermore, an understanding of the scan results and how to interpret them is also necessary.

There is a German article about Security DevOps – Angreifern (immer) einen Schritt voraus in the software engineering journal OBJEKTSpektrum. Architecture Overviewhttps://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgRXfiOaumuubUISZWdeF-kTsLDl-TqJfdR4BE2Q6o8VqcH0wMY2OCU10YGf6u89WatVntV9iYbb7Ixabcx7eitM5OvUtabsiWEnqML0lKYV8nohjrj9cMPHE8LFbdPQ63l73qivIXdZn6UUZVcN1DQ1b6e-nkaKVdRW3p13zqGzAhnAX9zHYZSEimv/s920/scb-architecture-svg.png UpgradingUpgraded Kubebuilder Version to v3The CRD’s are now using apiextensions.k8s.io/v1instead of apiextensions.k8s.io/v1beta1which requries at least Kubernetes Version 1.16 or higher. The Operator now uses the new kubebuilder v3 command line flag for enabling leader election and setting the metrics port. If you are using the official secureCodeBox Helm Charts for your deployment this has been updated automatically.

If you are using a custom deployment you have to change the --enable-leader-electionflag to --leader-electand --metrics-addrto --metrics-bind-address. For more context see: https://book.kubebuilder.io/migration/v2vsv3.html#tldr-of-the-new-gov3-plugin Restructured the secureCodeBox HelmCharts to introduce more consistency in HelmChart ValuesThe secureCodeBox HelmCharts for hooks and scanners are following a new structure for all HelmChart Values:

Instead of secureCodebox Version 2 example:

image:
image.repository — Container Image to run the scan
repository: owasp/zap2docker-stable
image.tag — defaults to the charts appVersion
tag: null
parserImage:
parserImage.repository — Parser image repository
repository: docker.io/securecodebox/parser-zap
pars[...]

___________________________
@hacking_Attack
@Hacking_Video

erImage.tag — Parser image tag
@default — defaults to the charts version
tag: null
parseJob:
parseJob.ttlSecondsAfterFinished — seconds after which the kubernetes job for the parser will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/
ttlSecondsAfterFinished: null
scannerJob:
scannerJob.ttlSecondsAfterFinished — seconds after which the kubernetes job for the scanner will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/
ttlSecondsAfterFinished: null
scannerJob.backoffLimit — There are situations where you want to fail a scan Job after some amount of retries due to a logical error in configuration etc. To do so, set backoffLimit to specify the number of retries before considering a scan Job as failed. (see: https://kubernetes.io/docs/concepts/workloads/controllers/job/#pod-backoff-failure-policy)
@default — 3
backoffLimit: 3 Added scanner.appendName to chart valuesUsing {{ .Release.name }} in the nmapHelmChart Name for scanTypescauses issues when using this chart as a dependency of another chart. All scanners HelmCharts already used a fixed name for the scanTypethey introduce, with one exception: the nmapscanner HelmChart.

The nmap exception was originally introduced to make it possible configure yourself an nmap-privilidgedscanType, which is capable of running operating system scans which requires some higher privileges: https://www.securecodebox.io/docs/scanners/nmap#operating-system-scans

This idea for extending the name of a scanType is now in Version 3 general available for all HelmCharts.

The solution was to add a new HelmChart Value scanner.appendNamefor appending a suffix to the already defined scanType name. Example: the scanner.nameAppend: -privilegedfor the ZAP scanner will create zap-baseline-scan-privileged, zap-api-scan-privileged, zap-full-scan-privilegedas new scanTypes instead of zap-baseline-scan, zap-api-scan, zap-full-scan. Renamed demo-apps to demo-targetsThe provided vulnerable demos are renamed from demo-appsto demo-targets, this includes the namespace and the folder of the helmcharts. Renamed the hook declarative-subsequent-scans to cascading-scansThe hook responsible for cascading scans is renamed from declarative-subsequent-scansto cascading-scans. Fixed Name Consistency In Docker Images / RepositoriesFor the docker images for scanners and parsers we already had the naming convention of prefixing these images with scanner-or parser-.

Hook images however were named inconsistently (some prefixed with hook-some unprefixed). To introduce more consistency we renamed all hook images and prefix them with hook-like we did with parser and scanner images.

Please beware of this if you are referencing some of our hook images in your own HelmCharts or custom implementations. Renamed lurcherto lurkerIn the 3.0 release, we corrected the misspelling in lurcher. To remove the remains after upgrade, delete the old service accounts and roles from the namespaces where you have executed scans in the past:

Find relevant namespaces
kubectl get serviceaccounts –all-namespaces | grep lurcher
Delete role, role binding and service account for the specific namespace
kubectl –namespace delete serviceaccount lurcher
kubectl –namespace delete rolebindings lurcher
kubectl –namespace delete role lurcher Removed Hook Teams WebhookWe implemented a more general notification hook which can be used to notify different systems like MS Teams and Slack and also Email based in a more flexible way with custom message templates. With[...]

___________________________
@hacking_Attack
@Hacking_Video

Kali Linux Tutorials
DongTai : Open-Source Passive Interactive Security Testing (IAST) Product

DongTai IASTis an open-source passive interactive security testing (IAST) product. It uses dynamic hooks and taint tracking algorithms to achieve universal vulnerability detection and multiples request associated with vulnerability detection (including but not limited to unauthorized vulnerabilities, overpower vulnerabilities), Third-party component vulnerability detection, etc. Currently, applications in Java and Python are supported for vulnerability detection. Project structure.
├── deploy
├── dongtai_common common functions and classes for each service to call
├── dongtai_conf configuration files
├── dongtai_engine vulnerability detection and vulnerability processing part
├── dongtai_protocol protocols for interaction between dongtai-server and agent
├── dongtai_web api for interacting with the web
├── static static files
└── test testcases ArchitectureDongTai IASThas multiple basic services, including DongTai-web, DongTai-webapi, DongTai-openapi, DongTai-engine, agent, DongTai-deploy, DongTai-Base-Imageand DongTai-Plugin-IDEA:

* DongTai-webis the product page of DongTai, which is used to handle the interaction between users and cave states.
* DongTai-webapiis responsible for handling user-related operations.
* DongTai-openapiis used to process the registration/heartbeat/call method/third-party component/error log data reported by agent, issue hook strategy, issue probe control commands, etc.
* DongTai-engineanalyzes whether there are vulnerabilities in HTTP/HTTPS/RPC requests according to the calling method data and taint tracking algorithm, and is also responsible for other related timing tasks.
* agentis a probe module of DongTai, including data collection terminals in different programming languages, used to collect data during application runtime and report to the DongTai-OpenAPIservice.
* DongTai-deployis used for the deployment of DongTai IAST, including docker-compose single-node deployment, Kubernetes cluster deployment, etc. If you want a deployment plan, you can add features or contribute to the deployment plan.
* DongTai-Base-Imagecontains the basic services that DongTai depends on runtime, including MySql, Redis.
* DongTai-Plugin-IDEAis the IDEA plug-in corresponding to the Java probe. You can run the Java probe directly through the plug-in and detect the vulnerabilities directly in IDEA. ScenarioThe usage scenarios of “DongTai IAST” include but not limited to:

* Embed the DevSecOpsprocess to realize automatic detection of application vulnerabilities/third-party component combing/third-party component vulnerability detection.
* Common vulnerability mining for open source software/open source components.
* Security testing before release, etc. Quick startDongTai IASTsupports SaaS Service and Localized Deployment. Please refer to Deployment Document for localized deployment.

* SaaS Version

* Fill out the Online Form to register an account.
* Log in to the [DongTai IAST] (https://iast.io).
* Have a quick start with Online Guideline.

* Localized Deployment Version DongTai IASTsupports a variety of deployment schemes which refer to Deployment Document:

* Stand-alone Deployment
* Docker-compose
* docker – pending upgrade

* Cluster Deployment
* Kubernetes Docker-composegit clone git@github.com:HXSecurity/DongTai.git
cd DongTai
chmod u+x build_with_docker_compose.sh
./build_with_docker_compose.sh Download

___________________________
@hacking_Attack
@Hacking_Video

this new hook in place it is not nessesary to maintain the preexisting MS Teams Hook any longer and therefore we removed it. Download

___________________________
@hacking_Attack
@Hacking_Video

Bussines logic error on p-store.net

Hello nama saya bagus lindu, kali ini saya menemukan kerentanan pada p-store.net, seperti yg kita tahu p-store.net adalah sebuah…Continue reading on Medium »
Read more...

How i Found Unauthorized Bypass RCE
https://medium.com/@yashshirke7806/how-i-found-unauthorized-bypass-rce-3591a86425a9?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Easy Vulnerability Leads To admin Console ,P1 typeContinue reading on Medium » (https://medium.com/@yashshirke7806/how-i-found-unauthorized-bypass-rce-3591a86425a9?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Anonymous hacker, who bragged about exploits on TikTok, says he was raided by Canadian police

https://external-preview.redd.it/od8BxKnQ-P706qbeObL1VFqfjUvkgWN1wfQLuHRureM.jpg?width=640&crop=smart&auto=webp&s=09467602c218d61c49a30b210ff8712f009a4723 submitted by /u/BollocksAsBalls
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
where to earn money?

I have heard about people earning some money with hacking like bug bounty and such? Now I was interested which things these are and how they work a d if its easy to do them because iam a programmer

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

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Is it possible reverse engineer a challenge, in order to crack a password from a NTLMv2 Authorization header?

Hello all,

Imagine the following environment: Couple of urlencoded form requests are done over http and there is an NTLMv2 authentication (the whole 3 yards). Then wireshark sniffs the packets and decodes them - I get mostly everything expected. My question is, is there a way to somehow decode the password? From what I get the mechanism works as follows - server sends a challenge (nonce) which is hashed using the client's password. Could I use the NTLMv2 Client Challenge and NTProofStr for that purpose and somehow reverse engineer the encoding?

Authorization header looks as follows:

```

NTLM TlRMTVNTUAADAAAAGAAYAFgAAAAOAQ4BcAAAAAwADAB+AQAADAAMAIo......

```

​

Excuse me if I'm asking borderline stupid questions, it's actually my first time diving into the cybersecurity realm.

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

___________________________
@hacking_Attack
@Hacking_Video

Directory Traversal 18rb Data Leaked
https://baguslindu.medium.com/directory-traversal-18rb-data-leaked-913c5843887a?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Hallo, sebenernya ini merupakan sesi iseng nulis write up, jadi begini pada tanggal 5 februari 2022 yang lalu saya melakukan sebuah…Continue reading on Medium » (https://baguslindu.medium.com/directory-traversal-18rb-data-leaked-913c5843887a?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Common C Vulnerabilities
https://medium.com/@capturethebugs/common-c-vulnerabilities-56ffad22581e?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

IntroductionContinue reading on Medium » (https://medium.com/@capturethebugs/common-c-vulnerabilities-56ffad22581e?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

How i Found Unauthorized Bypass RCE

Easy Vulnerability Leads To admin Console ,P1 typeContinue reading on Medium »
Read more...

Directory Traversal 18rb Data Leaked

Hallo, sebenernya ini merupakan sesi iseng nulis write up, jadi begini pada tanggal 5 februari 2022 yang lalu saya melakukan sebuah…Continue reading on Medium »
Read more...

Common C Vulnerabilities

IntroductionContinue reading on Medium »
Read more...