llocated at the runtime and typically contains program data. Exploitation is done by corrupting this data in specific ways to cause the application to overwrite internal structures such as linked list pointers.Stack Buffer Overflow Attack The most common Buffer Overflow attack known as the stack-based buffer overflow or vanilla buffer overflow attack consist of a stack is usually empty until and unless the program requires user input like a username or password. The program then writes a return memory address to the stack and then the user’s input is stored on top of it. While the stack is processed, the user’s input is sent to the return address specified by the program.

How Stack Buffer Overflow occurs Stack-based Buffer Overflows occurrence can be understood with the help of an example. We will be using a very simple C++ program to demonstrate stack-based buffer overflow/overrun.#include >buffer;In the above code, we used a character type variable and created an array named “buffer” which can store up to 8 bytes of data. This program waits for user input upon execution. Once a user puts data in the input field, the application stores the value in the allocated memory of 8 bytes. If the data supplied by the user is greater than 8 bytes, then it overwrites the adjacent memory locations resulting in termination of the process.___________________________
@hacking_Attack
@Hacking_Video

HItASIMUecxcdKUQCLcBGAsYHQ/s16000/12.png

___________________________
@hacking_Attack
@Hacking_Video

r-supplied input data was 14 bytes. These extra 6 bytes surpassed the buffer boundary overwriting the adjacent memory locations present in the stack. This created a segmentation fault resulting in stack smashing error.Windows Buffer Overflow Attack Pre-Requisites for Demonstrationdostackbufferoverflowgood.exeTesting/Analysis Machine: Microsoft Windows 10 1903Attacker Machine: Kali Linux 2020.1Debugger used: Immunity Debugger Immunity DebuggerImmunity Debugger is a tool that we can use for malware analysis, exploit writing and reverse engineering binary files. In this practical, we will use Immunity Debugger to see how buffer overflow occurs in a binary by analyzing the registers, hex values, memory addresses, etc. FuzzingFuzzing is a technique that is usually used in Black Box testing. In fuzzing some data is supplied in an automated fashion to the application to trigger the implementation bugs. This automation is done by a Fuzzer. ___________________________
@hacking_Attack
@Hacking_Video

Hacking Articles|Raj Chandel's Blog
A Beginner’s Guide to Buffer Overflow

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Windows 10 with Kali

https://cdn-images-1.medium.com/max/698/0*WyQsBydrDXmGE-aD.png
Do you use Kali? Do you use it with VMWare or Virtual Box? Do you know that you can use Kali without using any programs above? If not you…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

XSS made easy for testers, developers and managers

Let’s explore XSS but in a way that everyone can understandContinue reading on Medium »
Read more...

KubeArmor - Container-aware Runtime Security Enforcement System
http://www.kitploit.com/2021/05/kubearmor-container-aware-runtime.html

___________________________
@hacking_Attack
@Hacking_Video

Introduction to KubeArmor
KubeArmor is a container-aware runtime security enforcement system that restricts the behavior (such as process execution, file access, networking (https://www.kitploit.com/search/label/Networking) operation, and resource utilization) of containers (https://www.kitploit.com/search/label/Containers) at the system level. KubeArmor operates with Linux security modules (LSMs) (https://en.wikipedia.org/wiki/Linux_Security_Modules), meaning that it can work on top of any Linux platforms (such as Alpine, Ubuntu, and Container-optimized OS from Google) if Linux security modules (e.g., AppArmor (https://en.wikipedia.org/wiki/AppArmor), SELinux (https://en.wikipedia.org/wiki/Security-Enhanced_Linux), or KRSI (https://lwn.net/Articles/808048/)) are enabled in the Linux Kernel. KubeArmor will use the appropriate LSMs to enforce the required policies.
KubeArmor is designed for Kubernetes (https://www.kitploit.com/search/label/Kubernetes) environments; thus, operators only need to define security policies and apply them to Kubernetes. Then, KubeArmor will automatically detect the changes in security policies from Kubernetes and enforce them to the corresponding containers without any human intervention. If there are any violations against security policies, KubeArmor immediately generates audit logs with container (https://www.kitploit.com/search/label/Container) identities. If operators have any logging systems, it automatically sends audit logs to their systems as well.

___________________________
@hacking_Attack
@Hacking_Video

Functionality Overview
Restrict the behavior of containers at the system level Traditional container security solutions (e.g., Cilium) mostly protect containers by determining their inter-container relations (i.e., service flows) at the network level. In contrast, KubeArmor prevents malicious or unknown behaviors in containers by specifying their desired actions (e.g., a specific process should only be allowed to access a sensitive file). For this, KubeArmor provides the ability to filter process executions, file accesses, resource utilization, and even network operations (https://www.kitploit.com/search/label/Operations) inside containers at the system level. Enforce security policies to containers in runtime In general, security policies (e.g., Seccomp and AppArmor profiles) are statically defined within pod definitions for Kubernetes, and they are applied to containers at creation time. Then, the security policies are not allowed to be updated in runtime. To avoid this problem, KubeArmor maintains security policies separately, which means that security policies are no longer tightly coupled with containers. Then, KubeArmor directly applies the security policies into Linux security modules (LSMs) for each container according to the labels of given containers and security policies. Produce container-aware audit logs LSMs do not have any container-related information; thus, they generate audit logs only based on system metadata (e.g., User ID, Group ID, and process ID). Therefore, it is hard to figure out what containers cause policy violations. To address this problem, KubeArmor uses an eBPF-based system monitor, which keeps track of process life cycles in containers, and converts system metadata to container identities when LSMs generate audit logs for any policy violations from containers. Provide easy-to-use semantics for policy definitions KubeArmor provides the ability to monitor the life cycles of containers' processes and take policy decisions based on them. In general, it is much easier to deny a specific action but it is more difficult to allow only specific actions while denying all. KubeArmor manages internal complexities associated with handling such policy decisions and provides easy semantics towards policy language. Support network security enforcement among containers KubeArmor aims to protect containers themselves rather than interactions among containers. However, using KubeArmor a user can add policies that could apply policy settings at the level of network system calls (e.g., bind(), listen(), accept(), and connect()), thus somewhat controlling interactions among containers.
Getting Started
Please take a look at the following documents. Deployment Guide (https://github.com/accuknox/KubeArmor/blob/master/getting-started/deployment_guide.md) Security Policy Specification for Containers (https://github.com/accuknox/KubeArmor/blob/master/getting-started/security_policy_specification.md) Security Policy Examples for Containers (https://github.com/accuknox/KubeArmor/blob/master/getting-started/security_policy_examples.md) Security Policy Specification for Nodes (Hosts) (https://github.com/accuknox/KubeArmor/blob/master/getting-started/host_security_policy_specification.md) Security Policy Examples for Nodes (Hosts) (https://github.com/accuknox/KubeArmor/blob/master/getting-started/host_security_policy_examples.md) If you want to make a contribution, please refer to the following documents too. Contribution Guide (https://github.com/accuknox/KubeArmor/blob/master/contribution/contribution_guide.md) Development Guide (https://github.com/accuknox/KubeArmor/blob/master/contribution/development_guide.md) Technical Roadmap (https://github.com/accuknox/KubeArmor/blob/master/contribution/technical_roadmap.md)
Community

___________________________
@hacking_Attack
@Hacking_Video

Slack Please join the KubeArmor Slack channel (https://kubearmor.herokuapp.com/) to communicate with KubeArmor developers and other users. We always welcome having a discussion about the problems that you face during the use of KubeArmor.

Download KubeArmor (https://github.com/accuknox/KubeArmor)

___________________________
@hacking_Attack
@Hacking_Video

XSS made easy for testers, developers and managers
https://thexssrat.medium.com/xss-made-easy-for-testers-developers-and-managers-b404f744ec6b?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Let’s explore XSS but in a way that everyone can understandContinue reading on Medium » (https://thexssrat.medium.com/xss-made-easy-for-testers-developers-and-managers-b404f744ec6b?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
KubeArmor - Container-aware Runtime Security Enforcement System

https://1.bp.blogspot.com/-ZNrZMTqpELw/YJCRovR4XLI/AAAAAAAAWEw/EadZKBiG52kVHjjjNE0CX0zBo6MvV-t5ACNcBGAsYHQ/w640-h128/KubeArmor_1_logo.png Introduction to KubeArmorKubeArmor is a container-aware runtime security enforcement system that restricts the behavior (such as process execution, file access, networking operation, and resource utilization) of containers at the system level.

KubeArmor operates with Linux security modules (LSMs), meaning that it can work on top of any Linux platforms (such as Alpine, Ubuntu, and Container-optimized OS from Google) if Linux security modules (e.g., AppArmor, SELinux, or KRSI) are enabled in the Linux Kernel. KubeArmor will use the appropriate LSMs to enforce the required policies.
KubeArmor is designed for Kubernetes environments; thus, operators only need to define security policies and apply them to Kubernetes. Then, KubeArmor will automatically detect the changes in security policies from Kubernetes and enforce them to the corresponding containers without any human intervention.

If there are any violations against security policies, KubeArmor immediately generates audit logs with container identities. If operators have any logging systems, it automatically sends audit logs to their systems as well. https://1.bp.blogspot.com/-vEdy18LFix8/YJCRx5zsn_I/AAAAAAAAWE0/_AL2j-PDiAA5ITvgaOH6yW0xjsqS5tTdgCNcBGAsYHQ/w640-h356/KubeArmor_3_kubearmor_overview.png Functionality Overview* Restrict the behavior of containers at the system level

Traditional container security solutions (e.g., Cilium) mostly protect containers by determining their inter-container relations (i.e., service flows) at the network level. In contrast, KubeArmor prevents malicious or unknown behaviors in containers by specifying their desired actions (e.g., a specific process should only be allowed to access a sensitive file).

For this, KubeArmor provides the ability to filter process executions, file accesses, resource utilization, and even network operations inside containers at the system level.

* Enforce security policies to containers in runtime

In general, security policies (e.g., Seccomp and AppArmor profiles) are statically defined within pod definitions for Kubernetes, and they are applied to containers at creation time. Then, the security policies are not allowed to be updated in runtime.

To avoid this problem, KubeArmor maintains security policies separately, which means that security policies are no longer tightly coupled with containers. Then, KubeArmor directly applies the security policies into Linux security modules (LSMs) for each container according to the labels of given containers and security policies.

* Produce container-aware audit logs

LSMs do not have any container-related information; thus, they generate audit logs only based on system metadata (e.g., User ID, Group ID, and process ID). Therefore, it is hard to figure out what containers cause policy violations.

To address this problem, KubeArmor uses an eBPF-based system monitor, which keeps track of process life cycles in containers, and converts system metadata to container identities when LSMs generate audit logs for any policy violations from containers.

* Provide easy-to-use semantics for policy definitions

KubeArmor provides the ability to monitor the life cycles of containers' processes and take policy decisions based on them. In general, it is much easier to deny a specific action but it is more difficult to allow only specific actions while denying all. KubeArmor manages internal complexities associated with handling such policy decisions and provides easy semantics towards policy language.

* Support network security enforcement among containers

KubeArmor aims to protect containers themselves rather [...]

___________________________
@hacking_Attack
@Hacking_Video

than interactions among containers. However, using KubeArmor a user can add policies that could apply policy settings at the level of network system calls (e.g., bind(), listen(), accept(), and connect()), thus somewhat controlling interactions among containers. Getting StartedPlease take a look at the following documents.

1. Deployment Guide
2. Security Policy Specification for Containers
3. Security Policy Examples for Containers
4. Security Policy Specification for Nodes (Hosts)
5. Security Policy Examples for Nodes (Hosts)

If you want to make a contribution, please refer to the following documents too.

1. Contribution Guide
2. Development Guide
3. Technical Roadmap Community*
Slack

Please join the KubeArmor Slack channel to communicate with KubeArmor developers and other users. We always welcome having a discussion about the problems that you face during the use of KubeArmor. Download KubeArmor

___________________________
@hacking_Attack
@Hacking_Video

Any useful tool lists?
https://www.reddit.com/r/Pentesting/comments/n5ty6u/any_useful_tool_lists/

I've been playing around in my idle moments with various hardware tools and was curious if anyone knows of any lists of which tools are interesting and useful. So far I have played with: Digispark repurposed as a USB Rubber Ducky Proxmark Easy (a lot cheaper than the RDV4) ESP-RFID-TOOL (a quarter of the price of ESPkey) used with an HID pad Chameleon Mini Pro Yes I tend to go for the cheap alternatives, as this is not my profession, but this does give me a good understanding of the tools and their capability. So, any suggestions? submitted by /u/JDeMolay1314 (https://www.reddit.com/user/JDeMolay1314)
[link] (https://www.reddit.com/r/Pentesting/comments/n5ty6u/any_useful_tool_lists/) [comments] (https://www.reddit.com/r/Pentesting/comments/n5ty6u/any_useful_tool_lists/)

___________________________
@hacking_Attack
@Hacking_Video