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

Exploit Collector
Tagstoo 2.0.1 Cross Site Scripting / Code Execution

https://2.bp.blogspot.com/-n3YJZo98ptc/WWlvfHNo4ZI/AAAAAAAAIP8/W2JyxBpYTHMTjkJx5zl91eYOlgUDpw8egCLcBGAs/s1600/h84.png
Tagstoo version 2.0.1 suffers from a cross site scripting vulnerability that can lead to remote code execution.

MD5 | e4b6ab6f7999504181314036d2b0450f

Download
# Exploit Title: Tagstoo v2.0.1 - Stored XSS to RCE
# Exploit Author: TaurusOmar
# Twitter:@TaurusOmar
# HomePage:taurusomar.com
# Date: May 4th, 2021
# CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
# Risk: High (8.8)
# Vendor Homepage: https://tagstoo.sourceforge.io/
# Version: v2.0.1
# Tested on: Windows, Linux, MacOs

# Software Description:
Software to tag folders and files, with multimedia and epubs preview.
You can export data with the tagging information to a file, as backup or to import it in any computer.

# Vulnerability Description:

The software allows you to store payloads in the form of files or custom tags, once the malicious code is entered, the payload will be executed immediately.

The attacker can send a malicious file with the payload, when this file is opened, the chain will be executed successfully giving access to the
the remote attacker to get remote execution on the computer or directly open the folder in the program.

# Proof video
https://imgur.com/a/smeAjaW
# Payload 1: exec(calc)

#Decode Payload
#Encode Payload
x
# Payload 2: exec(netcat remote stolen file => /etc/passwd)

#Decode Payload
#Encode Payload

x

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
Trojan.Win32.Agent.xdtv Insecure Permissions

https://2.bp.blogspot.com/-swqN45HZtSI/WWlvXv0Z4fI/AAAAAAAAIOY/czRV0nNAPTIk5N0xfOCTXuQJzRjI48a4wCLcBGAs/s1600/h53.png
Trojan.Win32.Agent.xdtv malware suffers from an insecure permissions vulnerability.

MD5 | 07d0994f65fe6c84a13ec37c8cb643d8

Download
Discovery / credits: Malvuln - malvuln.com (c) 2021
Original source: https://malvuln.com/advisory/ffa9b76f9549a2c46415c855a0911e8a.txt
Contact: malvuln13@gmail.com
Media: twitter.com/malvuln

Threat: Trojan.Win32.Agent.xdtv
Vulnerability: Insecure Permissions
Description: The malware creates an insecure installation dir under "C:\Program Files (x86)" and grants full (F) permissions to the Everyone user group. Standard users can rename the executables dropped by the malware to disable it or replace it with their own executable. Then wait for a privileged user to logon to the infected machine to potentially escalate privileges.
Type: PE32
MD5: ffa9b76f9549a2c46415c855a0911e8a
Vuln ID: MVID-2021-0198
Disclosure: 05/04/2021

Exploit/PoC:
C:\>cacls "C:\Program Files (x86)\Cannonnt"
C:\Program Files (x86)\Cannonnt Everyone:(OI)(CI)F

C:\>cd "\Program Files (x86)\Cannonnt"

C:\Program Files (x86)\Cannonnt>dir
Volume in drive C has no label.

Directory of C:\Program Files (x86)\Cannonnt

05/10/2012 05:04 PM 53,248 messenger.exe
05/10/2012 05:04 PM 122,880 rdbms.exe
05/10/2012 05:04 PM 196,608 RDS.exe
05/10/2012 05:04 PM 233,472 windns.exe
4 File(s) 606,208 bytes

Disclaimer: The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information or exploits by the author or elsewhere. Do not attempt to download Malware samples. The author of this website takes no responsibility for any kind of damages occurring from improper Malware handling or the downloading of ANY Malware mentioned on this website or elsewhere. All content Copyright (c) Malvuln.com (TM).

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
Markdown-Explorer 0.1.1 Cross Site Scripting / Code Execution

https://1.bp.blogspot.com/-HfAgGXf1DOw/WWlvbMysVAI/AAAAAAAAIPI/FubFag34U7YDsw4ZG5KiakYQR-P9HSuiwCLcBGAs/s1600/h72.png
Markdown-Explorer version 0.1.1 suffers from a cross site scripting vulnerability that can lead to remote code execution.

MD5 | fc8011faa7d4469e905701a412002aa4

Download
# Exploit Title: Markdown-Explorer 0.1.1 XSS to RCE
# Exploit Author: TaurusOmar
# Twitter:@TaurusOmar
# HomePage:taurusomar.com
# Date: May 4th, 2021
# CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
# Risk: High (8.8)
# Vendor Homepage: https://github.com/jersou/markdown-explorer
# Version: 0.1.1
# Tested on: Windows, Linux, MacOs

# Software Description:
Easily explore, view and edit markdown documentation of a file tree.
If your projects documentation is written in Markdown, with md files dispersed throughout your project tree, Markdown Explorer displays md files in a tree structure, and it allows filtering by file name or by file content.
Just drop a folder on the window (or click on the folder icon on top left) to show the Markdown documentation of this folder. Then, explore the tree on the left, and toggle view/edit mode on md file with the button on the top right.
# Vulnerability Description:
The software allows you to store payloads within its own editor, as well as upload (.md) files once malicious code is entered, the payload will be executed immediately.
The attacker can send a malicious file with the payload, when this file is opened, the chain will be executed successfully giving access to
the remote attacker to get remote execution on the computer.
#Proof
https://imgur.com/a/w4bcPWs
# Payload : exec(Attacker Reverse netcat stolen => /etc/passwd) && exec(calc)

[](http://)


Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
SnipCommand 0.1.0 Cross Site Scripting / Code Execution

https://4.bp.blogspot.com/-sHG2jViTb-c/WWlvSCf2XfI/AAAAAAAAINY/YxfxwjOK_o05QB9TpuqqysTdHaIb3yf8wCLcBGAs/s1600/h36.png
SnipCommand version 0.1.0 suffers from a cross site scripting vulnerability that can lead to remote code execution.

MD5 | 34dc1fa9d8c9fea6965bfb141eda50dc

Download
# Exploit Title: SnipCommand 0.1.0 XSS to RCE
# Exploit Author: TaurusOmar
# Twitter:@TaurusOmar
# HomePage:taurusomar.com
# Date: May 4th, 2021
# CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
# Risk: High (8.8)
# Vendor Homepage: https://github.com/gurayyarar/SnipCommand
# Version: 0.1.0
# Tested on: Windows, Linux, MacOs

# Software Description:
Open source command snippets manager for organize and copy fast.
It helps you create, organize and store your commands (Excel formulas, Sql Queries, Terminal commands, etc.) with dynamic parameters for quick copy to it. Describe your commands with dynamic parameters also support documentation about your snippets. You can select or specify your dynamic values using with selectbox/inputbox for ready to paste the workspace. You can organize with tags.
# Vulnerability Description:
The software allows you to store payloads in the form of files or as titles in their dynamic values, once the malicious code is entered, the payload will be executed immediately.
The attacker can send a malicious file with the payload, when this file is opened, the chain will be executed successfully giving access to the
the remote attacker to get remote execution on the computer.

#Proof video
https://imgur.com/a/I2reH1M
# Payload: exec(Attacker Reverse netcat stolen => /etc/passwd) && exec(calc)

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video