Hacking on Medium
O que é privacidade!?

https://cdn-images-1.medium.com/max/1125/1*pR1NjXrr-yte3zw8rHnafQ.jpeg
Acredito que muitos já tem conhecimento de que ninguém tem uma real e completa segurança ou privacidade, mas para aqueles que buscam um…

Continue reading on Medium »

Hacking on Medium
Why Does Cyber Security Seem As Headache?

https://cdn-images-1.medium.com/max/2600/0*s69jcYwB5Oj3eYMm
Is it impossible or too hard to handle?

Continue reading on PrimeThreat »

SGXRay - Automating Vulnerability Detection for SGX Apps

Intel SGX protects isolated application logic and sensitive data inside an enclave with hardware-based memory encryption. To use such hardware-based security mechanism requires a strict programming model on memory usage， with complex APIs in and out the enclave boundary. Enclave developers are required to apply careful programming practices to ensure enclave security, especially when dealing with data flowing across the enclave's trusted boundary. Trusted boundary violations can further cause memory corruption and are exploitable by attackers to retrieve and manipulate protected data. Currently, no publicly available tools can effectively detect such issues for real-world enclaves.SGXRay is an automated reasoning tool based on the SMACK verifier that automatically detects SGX enclave bugs rooting from violations of trusted boundaries. It recompiles a given enclave code and starts the analysis from a user-specified enclave function entry. After the analysis, it either finds an invalid pointer handling inside an SGX software stack such as deferencing unchecked pointer inside an enclave, invalid memory deallocation, and TOCTOU bugs, or prove the absense of such bugs up to a user-specified loop and recursion bound. Currently, SGXRay SGX applications built on two SGX SDKs: Intel SGX SDK and openenclave SDK. Users can opt in SDK code for a more thorough analysis. Getting Started For a quick start, please follow a step-by-step tutorial on using SGXRay over one of the demo examples here. The following figure demonstrates the workflow of SGXRay. Running SGXRay is a two-step process. The first step is to obtain an LLVM IR file for the application. The second step is to invoke SGXRay CLI for verification. For the first step, we provide two Docker images for each SDK, respectively. docker pull baiduxlab/sgx-ray-frontend-inteldocker pull baiduxlab/sgx-ray-frontend-oe The detailed instructions to run the first step can be found here. For the second step, we also provide a Docker image. docker pull baiduxlab/sgx-ray-distro:latest The detailed instructions to run the second step can be found here. Docker Build We provide a Dockerfile that builds the image for the verification step. git clone https://github.com/baiduxlab/sgxray.git && cd sgxraydocker build . -t sgx-ray-distro-local --build-arg hostuid=$UID -f Dockerfiles/Dockerfile-CLI Successful build should produce an image named sgx-ray-distro-local which has an user user with the same user id as the host account. Documentations Detailed documentations of SGXRay can be found as follows. LLVM IR Generation Verification Download Sgxray
Read more...

SGXRay - Automating Vulnerability Detection for SGX Apps
http://www.kitploit.com/2021/08/sgxray-automating-vulnerability.html

Intel SGX protects isolated application logic and sensitive data inside an enclave with hardware-based memory encryption. To use such hardware-based security mechanism requires a strict programming model on memory usage， with complex APIs in and out the enclave boundary. Enclave developers are required to apply careful programming practices to ensure enclave security, especially when dealing with data flowing across the enclave's trusted boundary. Trusted boundary violations can further cause memory corruption and are exploitable by attackers to retrieve and manipulate protected data. Currently, no publicly available tools can effectively detect such issues for real-world enclaves.
SGXRay is an automated (https://www.kitploit.com/search/label/Automated) reasoning tool based on the SMACK (http://smackers.github.io/) verifier that automatically detects SGX enclave bugs rooting from violations of trusted boundaries. It recompiles a given enclave code and starts the analysis (https://www.kitploit.com/search/label/Analysis) from a user-specified enclave function entry. After the analysis, it either finds an invalid pointer handling inside an SGX software stack such as deferencing unchecked pointer inside an enclave, invalid memory deallocation, and TOCTOU bugs, or prove the absense of such bugs up to a user-specified loop and recursion bound. Currently, SGXRay SGX applications built on two SGX SDKs: Intel SGX SDK and openenclave SDK. Users can opt in SDK code for a more thorough analysis.
Getting Started
For a quick start, please follow a step-by-step tutorial on using SGXRay over one of the demo examples here (https://github.com/baiduxlab/sgxray/blob/main/docs/tutorial.md). The following figure demonstrates the workflow of SGXRay.

Running SGXRay is a two-step process. The first step is to obtain an LLVM IR file for the application. The second step is to invoke SGXRay CLI for verification. For the first step, we provide two Docker images for each SDK, respectively. docker pull baiduxlab/sgx-ray-frontend-intel
docker pull baiduxlab/sgx-ray-frontend-oe The detailed instructions to run the first step can be found here (https://github.com/baiduxlab/sgxray/blob/main/docs/bc-production.md). For the second step, we also provide a Docker image. docker pull baiduxlab/sgx-ray-distro:latest The detailed instructions to run the second step can be found here (https://github.com/baiduxlab/sgxray/blob/main/docs/verification.md).
Docker Build
We provide a Dockerfile (https://www.kitploit.com/search/label/Dockerfile) that builds the image for the verification step. git clone https://github.com/baiduxlab/sgxray.git && cd sgxray
docker build . -t sgx-ray-distro-local --build-arg hostuid=$UID -f Dockerfiles/Dockerfile-CLI Successful build should produce an image named sgx-ray-distro-local which has an user user with the same user id as the host account.
Documentations
Detailed documentations of SGXRay can be found as follows. LLVM IR Generation (https://github.com/baiduxlab/sgxray/blob/main/docs/bc-production.md) Verification (https://github.com/baiduxlab/sgxray/blob/main/docs/verification.md)

Download Sgxray (https://github.com/baiduxlab/sgxray)

hacking: security in practice
Using an Android Phone as a Rubber Ducky

https://external-preview.redd.it/tIRXlv39aCLHeLjE1K6dJwK8VfL2s7SHuitQBiNqxJI.jpg?width=640&crop=smart&auto=webp&s=adc92b70c006f5335dcbecaeecb095ab6fa57287 submitted by /u/PCtheawesome1
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
File upload filter

Hi guys, need some info. For pen-testing purposes, I have been trying to upload a php shell but there is a filter which only allows jpg files. I tried all the techniques (double extension, hex numbers) but it won’t work. It is a server side filter. Please advice, thanks.

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

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Anyone ever utilise Visual Studio for making payloads?

I saw this article online where basically a person makes a simple msfvenom reverse shell payload in C. Imports it into Visual Studio and uses a random template and exports it as an exe. Keep in mind I'm not much of a coder especially in C so bear with me. In any case does anyone else make payloads like this? If had a small amount of success using this method. Bypassing Avast, BitDefender, Ad-Aware, eScan, McAfee and a few others with which I hadn't had much luck before. Never sadly managed to get 64 bit payloads working because of my poor knowledge of C and Visual Studio, if anyone else managed to get some where with theese methods I'd love to hear your thoughts and experiences. Thanks!

Edit: Here's the article by the way, https://www.virtuesecurity.com/evading-antivirus-with-better-meterpreter-payloads/

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

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
SGXRay - Automating Vulnerability Detection for SGX Apps

http://4.bp.blogspot.com/-4hgPuw86v5E/YRYFUSia88I/AAAAAAAAp2I/1hDgGwME-_QAyKbtCFgVppG-UveAKynmQCK4BGAYYCw/w640-h248/sgxray_1_sgxray-796717.png Intel SGX protects isolated application logic and sensitive data inside an enclave with hardware-based memory encryption. To use such hardware-based security mechanism requires a strict programming model on memory usage， with complex APIs in and out the enclave boundary. Enclave developers are required to apply careful programming practices to ensure enclave security, especially when dealing with data flowing across the enclave's trusted boundary. Trusted boundary violations can further cause memory corruption and are exploitable by attackers to retrieve and manipulate protected data. Currently, no publicly available tools can effectively detect such issues for real-world enclaves.
SGXRay is an automated reasoning tool based on the SMACK verifier that automatically detects SGX enclave bugs rooting from violations of trusted boundaries. It recompiles a given enclave code and starts the analysis from a user-specified enclave function entry. After the analysis, it either finds an invalid pointer handling inside an SGX software stack such as deferencing unchecked pointer inside an enclave, invalid memory deallocation, and TOCTOU bugs, or prove the absense of such bugs up to a user-specified loop and recursion bound.

Currently, SGXRay SGX applications built on two SGX SDKs: Intel SGX SDK and openenclave SDK. Users can opt in SDK code for a more thorough analysis. Getting StartedFor a quick start, please follow a step-by-step tutorial on using SGXRay over one of the demo examples here.

The following figure demonstrates the workflow of SGXRay. http://4.bp.blogspot.com/-4hgPuw86v5E/YRYFUSia88I/AAAAAAAAp2I/1hDgGwME-_QAyKbtCFgVppG-UveAKynmQCK4BGAYYCw/w640-h248/sgxray_1_sgxray-796717.png Running SGXRay is a two-step process. The first step is to obtain an LLVM IR file for the application. The second step is to invoke SGXRay CLI for verification.

For the first step, we provide two Docker images for each SDK, respectively. docker pull baiduxlab/sgx-ray-frontend-intel
docker pull baiduxlab/sgx-ray-frontend-oeThe detailed instructions to run the first step can be found here.

For the second step, we also provide a Docker image. docker pull baiduxlab/sgx-ray-distro:latestThe detailed instructions to run the second step can be found here. Docker BuildWe provide a Dockerfile that builds the image for the verification step. git clone https://github.com/baiduxlab/sgxray.git && cd sgxray
docker build . -t sgx-ray-distro-local --build-arg hostuid=$UID -f Dockerfiles/Dockerfile-CLISuccessful build should produce an image named sgx-ray-distro-localwhich has an user userwith the same user id as the host account. DocumentationsDetailed documentations of SGXRay can be found as follows.

* LLVM IR Generation
* Verification Download Sgxray

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
O xss ocorre quando o invasor é capaz de injetar um script, geralmente em JavaScript, em páginas…

https://cdn-images-1.medium.com/max/1200/1*SrIDxNj1SlSl4rcEkqaehQ.png
Xss refletido, já ouviu falar sobre XSS?

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
TryHackMe Write-up: Wonderland

https://cdn-images-1.medium.com/max/1962/1*9V-jvoi3s4M88OmI8FiCFA.png
Dificultad: Media

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

building pentesting as services platform
https://www.reddit.com/r/Pentesting/comments/p6gns5/building_pentesting_as_services_platform/

i am building pen testing as service platform to be sold to pen testing firms or enterprise that has internal teams #### some features: it makes it easy to collaborate between team members sharing notes ,files make it easy to collaborate between client or product teams and pen testing teams at real time instead of waiting for finishing of pentest Can be intgereted with other ticket system like jira,service now ..etc can generate the default docx report also has some embedded frameworks checklists tracking performance of pentesters Like point system #### i have some questions: what will be fair price for that ? what features may i need to add ? submitted by /u/MarsupialNew3737 (https://www.reddit.com/user/MarsupialNew3737)
[link] (https://www.reddit.com/r/Pentesting/comments/p6gns5/building_pentesting_as_services_platform/) [comments] (https://www.reddit.com/r/Pentesting/comments/p6gns5/building_pentesting_as_services_platform/)

___________________________
@hacking_Attack
@Hacking_Video