hacking: security in practice
Why hasn’t the Advanced Encryption Standard(AES) never been compromised?

It’s believed the AES-256 is vulnerable if an attacker can access a user's key. This is why AES is just one aspect of keeping data secure.

There has yet to be a single instance of AES-256 ever being hacked into, at least non ever documented, but that hasn't been for a lack of trying.

The first crack attempts at AES was in 2011, against AES-128 encryption where a biclique attack was used. Biclique is around four times faster at attacking encryption than the standard brute force attack seen most often. It failed.

However a team of Microsoft and Dutch researchers have released a report detailing a theoretical attack on the Advanced Encryption Standard (AES).

The attack, to be presented in early December, utilizes a complex process known as biclique analysis that advances a technique that originally targeted just hashing algorithms.

I also want to address the elephant in the room, which is ‘military-grade’ doesn’t actually exist. At least not in the terms “average handy thinks it is”

The US military uses the military-grade AES encryption algorithm on two fronts. The first being secret (unclassified) information is specific to AES-128.

The second is for top-secret (classified) information, which uses AES-256. Whenever information is handled on both levels through a single entity, AES-256 is adopted as the standard AES encryption algorithm.

Encryption is basically chopping up information into something incoherent.

Military-grade encryption is AES-256, which differs from AES-128 and AES-192 by having a larger key size in the AES encryption algorithm.

Essentially, AES-256 uses more processing power to encrypt and decrypt information making it more difficult for intruders to crack.

But lets be honest, It would take upwards of a billion years for an attack to force its way through a 126-bit key, let alone AES-128. So long as the data encryption has been implemented properly, there is no known attack that would compromise the protection afforded by AES.

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

___________________________
@hacking_Attack
@Hacking_Video

Dark Reading: Attacks/Breaches
Threat Intelligence Services Are Universally Valued by IT Staff

Most of those surveyed are concerned about AI-based attacks and deepfakes, but suggest that their organization is ready.

Hacking on Medium
HackThisSite Extended Basic 13 Mission

https://cdn-images-1.medium.com/max/700/0*YQhdHgy3Rl6bRtOC.jpg
Problem

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Enumeration of Email address using registration functionality API in WealthSimple

https://cdn-images-1.medium.com/max/1341/1*1MnMXqoH1nifxFI5ahytQQ.png
Description

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
WealthSimple Application fails to protect against password spraying

https://cdn-images-1.medium.com/max/1341/1*jtzgBQxsZ56VHbKOseCUUA.png
WealthSimple application allows a user to login by using the API “https://api.production.wealthsimple.com/v1/oauth/v2/token". There are 2…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

DEF CON Groups VR Events
https://www.reddit.com/r/Pentesting/comments/vk582t/def_con_groups_vr_events/

___________________________
@hacking_Attack
@Hacking_Video

submitted by /u/NeverDoubtGreatness (https://www.reddit.com/user/NeverDoubtGreatness)
[link] (https://www.dcgvr.org/cfp.html) [comments] (https://www.reddit.com/r/Pentesting/comments/vk582t/def_con_groups_vr_events/)

___________________________
@hacking_Attack
@Hacking_Video

How I stopped hunting on HackerOne after years because they stole my $50k. And so should you.
https://medium.com/@skavans_/how-i-stopped-hunting-on-hackerone-after-years-because-they-stole-my-50k-and-so-should-you-7328b8af30f1?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

You may have heard about Belarusian security researcher xnwup and the story of blocking his $25k on HackerOne. It was pretty resonant at…Continue reading on Medium » (https://medium.com/@skavans_/how-i-stopped-hunting-on-hackerone-after-years-because-they-stole-my-50k-and-so-should-you-7328b8af30f1?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

How I stopped hunting on HackerOne after years because they stole my $50k. And so should you.

You may have heard about Belarusian security researcher xnwup and the story of blocking his $25k on HackerOne. It was pretty resonant at…Continue reading on Medium »
Read more...

hacking: security in practice
I am a troll

oh Great Londini expose me.

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

Kali Linux Tutorials
NodeSecurityShield : A Developer And Security Engineer Friendly Package For Securing NodeJS Applications

NodeSecurityShield is a Developer and Security Engineer friendly package for Securing NodeJS Applications.

Inspired by the log4J vulnerability (CVE-2021-44228) which can be exploited because an application can make arbitrary network calls.

We felt there is an need for an application to declare what privileges it can have so that exploitation of such vulnerabilities becomes harder.

To achieve this, NSS (Node Security Shield) has Resource Access Policy.

Resource Access Policy (RAP)

Resource Access Policy is similar to CSP(Content Security Policy).

It lets the developer/security engineer declare what resources an application should access. And Node Security Shield will enforce it.

Installation

Install Node Security Shield using npm

npm install nodesecurityshield

Usage

// Require Node Security Shield
let nodeSecurityShield = require(‘nodesecurityshield’);
// Enable Attack Monitoring and/or Blocking
nodeSecurityShield.enableAttackMonitoring(resourceAccessPolicy ,callbackFunction);

Sample resourceAccessPolicy

const resourceAccessPolicy = {
“outBoundRequest” : {
“blockedDomains” : [“.123.com”, “stats.abc.com”, ‘xyz.com’], “allowedDomains” : [“.domdog.io”]
}
};

Sample callbackFunction for Attack Monitoring

var callbackFunction = function (violationEvent) {
console.log(violationEvent);
}

Sample callbackFunction for Attack Blocking

var callbackFunction = function (violationEvent) {
throw new Error(“Request Blocked. It violates declared Resource Access Policy.”)
}

Integrating with Sentry

Sample resourceAccessPolicyto integrate with Sentry

const resourceAccessPolicy = {
“reportUriHosts” : [“ingest.sentry.io”],
“outBoundRequest” : {
“blockedDomains” : [“.123.com”, “stats.abc.com”, ‘xyz.com’], “allowedDomains” : [“.domdog.io”]
}
};

Features

* Attack Monitoring
* Outbound Network Calls

* Attack Blocking
* Outbound Network Calls
Download

Kali Linux Tutorials
Chlonium : Chromium Cookie Import / Export Tool

Chlonium is an application designed for cloning Chromium Cookies.

From Chromium 80 and upwards, cookies are encrypted using AES-256 GCM, with a state key which is stored in the Local State file. This state key is encrypted using DPAPI. This is a change from older versions, which used DPAPI to encrypt each cookie item in the cookie database. What this means is that if you have the state key, you will always be able to decrypt the cookie database offline, without needing continual access to DPAPI keys.

This essentially makes cookie databases “portable”, meaning they can be moved from machine to machine, provided you have dumped the state key. The cookies themselves need to be re-encrypted when they are imported, because the state keys will differ on each user profile & machine. This can be done using the same process as decryption, by first decrypting the state key from the “target” browser, and then re-encrypting each item with the new key.

The project is written in C# and has two separate components to it. The first component, chlonium.exeis the collector binary. It simply decrypts the state key and prints it. Keep a note of this key and you can decrypt cookies in the future by downloading the Cookiesdatabase file whenever you need updated cookies. By default it will attempt to decrypt the Chrome state key. If you want to dump the state key for another browser (e.g. Edge), you can specify a path to the key.

For example:

Chlonium.exe “c:\users\user\AppData\Local\Microsoft\Edge\User Data\Local State”
[+] Statekey = 3Cms3YxFXVyJRUbulYCnxqY2dO/jubDkYBQBoYIvqfc=

The second component, ChloniumUI.exeis the “importer” tool. This takes care of decrypting a given Cookies database file with a given state key, re-encrypting the values with the current users state key, and importing the cookies into your chosen browser. You run this on the machine you want to import the cookies into.

To use it, run the ChloniumUI.exeexecutable. Enter the previously extracted state key, choose the Cookiesfile you wish to import, and select the browser you wish the import the cookies into. Now click “Import Cookies” and the cookies will be imported. ChloniumUIcurrently supports three Chromium based browsers: Edge, Chrome and Vivaldi. Additional browsers can be added in Browsers.cs. This adds the unintended benefit of being able to import an Edge cookie file into Chrome, or vice versa (for example), though it’s probably not a good idea given that the user-agent will mismatch.

Important Note: When importing the cookie file into your browser, all old cookies are cleared! A backup is copied to the current directory (with relevant time stamp). If you need to restore the previous cookies, simply copy the backup file over the Cookiesfile. WhyTools such as Mimikatz and SharpChromium already have the capability to dump Chrome 80 cookies, why another tool?

This tool is specifically aimed at making it easier to import cookies into another browser. Whilst these tools do a great job of dumping Chromium cookies (and more!), I wanted to have something that let me easily import into another browser. Third-party cookie manager plugins exist, but I’ve always found these fiddly and prone to failure. CloniumUIis designed to make this process easier by importing the cookies directly into your browser’s sqlite database.

Whilst this project comes with the chlonium.execollector, which aids in dumping the state key, this is really only an example. Other tools such as Mimikatz will also dump the state key for you, in a potentially stealthier way (depending on your operating environment, execution method etc.). Additionally, SharpDPAPI will allow you to decrypt the Chromium state key file if you have DPAPI state keys, current password, [...]

or domain backup key – allowing you to dump cookies remotely over SMB!

When carrying out Red Teaming, I sometimes need to dump a user’s cookies multiple times over a sustained period (e.g. daily/weekly). Using a .NET assembly, Reflective DLL or other in-memory execution technique to extract individual cookies from the cookie file directly on the target system is unneccesary and exposes the operator to increased risk of detection. Instead you can simply dump the state key once, and copy the Cookiesdatabase file off whenever you need fresh cookies, without requiring additional execution. Password Import/ExportChloniumUIalso supports password import and export. To use this feature, simply supply the Login Datadatabase path instead of the Cookiesdb, along with the state key, and select the browser you wish to import them into (for export this doesn’t matter). This allows you to either export passwords in plaintext to a file, or import them into your browser. As with cookies, you can import Chrome passwords into Edge, Edge passwords into Vivaldi etc. Offline Statekey DecryptionChlonium supports offline state key decryption whereby you can decrypt the users statekey offline if you have all of the following files:

* The Local State file from: C:\Users\<user\AppData\Local\<browser\User Data\Local State* The DPAPI masterkey files from: C:\Users\<user\AppData\Roaming\Microsoft\Protect\<sid\and one of the following:

* Domain backup key .pvk file (e.g. from NTDS.dit)
* Domain backup key in base64 (e.g. from Mimikatz/SharpDPAPI LsaRetrievePrivateDataAPI method)
* The user’s password

Now simply provide these values under the “Offline statekey decryption” tab, and Chlonium will attempt to decrypt the encrypted statekey by first decrypting the DPAPI masterkeys (using the backup key or password), and then using these keys to decrypt the statekey. Once the statekey is decrypted, this can be used in the “Import or Export Database” tab to retrieve cookies/passwords.

Usage Note: When using the user’s password to decrypt the DPAPI masterkey, Chlonium will first attempt to extract the user’s SID from the BK-<netbiosdomainnamefile from within the DPAPI masterkey folder. If this fails (or if the file does not exist), it will try to get the SID from the DPAPI masterkey folder name instead (which by default will be named after the user’s SID). If you have renamed the folder, or do not have a copy of the BK file, you will not be able to decrypt the masterkey using a password.

This feature makes use of the excellent SharpChrome and SharpDPAPI projects by @harmj0y. Full credit goes to the original authors of SharpDPAPI. DetectionSet a SACL on the Chrome Local Stateand Cookiesfiles (as well as other sensitive files such as Login Dataand History). Look for suspicious (e.g. non browser related) processes opening any of these files.

Take a look at this great blog post from @cryps1s about setting up SACLs for detection.

For AV vendors that use a file system filter driver, consider blocking non browser-related processes from opening these files. e.g. PowerShell opening the Cookiesfile. Download

Assets Discovery solution to discover all technologies used by a company
https://www.reddit.com/r/Pentesting/comments/vk8kwx/assets_discovery_solution_to_discover_all/