Dark Reading: Attacks/Breaches
DigiCert Advances Passwordless Authentication with Support for Windows Hello for Business

Managing Windows Hello hybrid certificate trust model on DigiCert PKI platform streamlines enterprise passwordless authentication and access, an industry first for public Certification Authorities (CAs).

___________________________
@hacking_Attack
@Hacking_Video

Dark Reading: Attacks/Breaches
Virtual-Network Vulnerability Found in AWS, Other Clouds

The privilege-escalation flaws affect Amazon WorkSpaces and more than a dozen services that use a particular implementation of USB over Ethernet.

Dark Reading: Attacks/Breaches
Rubrik's New Managed Service Protects Data from Ransomware Attacks

Rubrik Cloud Vault provides data recovery assurance against ransomware attacks for Microsoft Azure customers, even if they maintain a hybrid environment.

Dark Reading: Attacks/Breaches
Cerberus Sentinel Announces Acquisition of Arkavia Networks

U.S. cybersecurity services firm expands internationally into Latin America.

___________________________
@hacking_Attack
@Hacking_Video

Dark Reading: Attacks/Breaches
Google Disrupts Botnet Targeting Windows Machines

The company has also launched litigation against the Glupteba botnet, marking the first lawsuit against a blockchain-enabled botnet.

___________________________
@hacking_Attack
@Hacking_Video

Pentesting Book Recommendations
https://www.reddit.com/r/Pentesting/comments/rbayjj/pentesting_book_recommendations/

Webdev here looking to learn more about security in general. What books do you recommend I dig into? submitted by /u/sambomambowambo (https://www.reddit.com/user/sambomambowambo)
[link] (https://www.reddit.com/r/Pentesting/comments/rbayjj/pentesting_book_recommendations/) [comments] (https://www.reddit.com/r/Pentesting/comments/rbayjj/pentesting_book_recommendations/)

___________________________
@hacking_Attack
@Hacking_Video

Hacking Articles|Raj Chandel's Blog
Explore Hackthebox Walkthorugh

"Explore" is a Capture the Flag challenge that we'll be solving today. (HTB) Hack the Box is where you can get your hands on one, this box is based on ADB (Android Debug Bridge). So, let’s get started and learn how to break it down successfully. So, let's get started and learn how to split it down effectively. Pentesting Methodology· Port Scanning & Enumeration· Exploitation· Privilege Escalation Nmapnmap -p- -sV 10.129.198.246https://blogger.googleusercontent.com/img/a/AVvXsEhlXOSVcNFAaX64tKsKltt8glvxbQ91HexcxLWu5FC_yicPbJ1LNbuTiELMwYZemwhbATYK3YeNh2a7nsiZQ7H554HBzByQ0zpOIGPgA9azAB5CXEWsngs88dRz0W_m-lixc1lDxMb95e3n4KRA81f4_GeAJJQYSfXZNpBXJ6MMSmaEtL42dBw-qk-YDA=s16000 According to the nmap output, we geton port 2222 SSH server runningon port 59777HTTP service runningon port 5555 a TCP service running While searching for port 59777 on the internet, we come up with the following GitHub as the first resultExploitationCopy the path from the GitHub URL to our Kali System so that we may get the file.git clone https://github.com/fs0c131y/ESFileExplorerOpenPortVuln list https://blogger.googleusercontent.com/img/a/AVvXsEj16IaXaqyvPhbRAbkZcKW4LqE7ZxKm0vyn7EiWnXWmMCiKnejZutiuvP8BqKdzL3YrMwwyPrQUmsZBBmb65HenOHaD-sUewD_OTIt76U3TVTHPbb-Z3lh7oiBcPw5WqgoGNkpXDC3xSFLhYoWcS1mWVEzafJL3HfW99ab9N7DyEqI4TSTLBCRWb5Od3A=s16000 There is a python exploit script that we can use to see if anything can be found. We get the creds.jpg file, the name "creds" gives us an indication that it may include the credentials, which are the login id and password that may be used for SSH later on.python poc.py --cmd listPics --ip 10.129.198.246 -g /storage/emulated/0/DCIM/creds.jpg --ip 10.129.198.246https://blogger.googleusercontent.com/img/a/AVvXsEjXT03AWFh7ZTgdl68fPMIs9M_7EW2rjGxsB6tWvy1dI_cT5mRlI0hLKQ36MOvG0p7z7rAuXikemQdHNpoqAiPLAObJCTFx5yDPLKlIyBX1TGO0LbrAm35hJaHEXR2TN6yXdvJrglcKRUVsstV57Vju1pOwJvbuklsEDPUI-7HUxSAPO2JTm3e181HRpQ=s16000 Ahh, the file seemed to contain a username and password.Username: KristiHaving remembered that an SSH port was open on 2222, I attempted to SSH into the machine using these credentials.ssh kristi@10.129.198.246 -p 2222https://blogger.googleusercontent.com/img/a/AVvXsEhazVbLwOpRyN55X_oOmjLBDPq6tqi3CJwWjmnvHJmP67mH1dgxZoeUjyOFrwdeSMD4Q8NqAw-A4htlf32vv0t77j5Gh5fVtyUf8zMNxP9FMVfPq20HeuinQ14uKTc4UOUt89xqTs3iVwlBMHyl--eFdxp5YYhV7nfZGoTkgDL7wmWw34Tcg8oKWxRJKg=s16000 Privilege EscalationAn ADB service is running on port 5555, and we have SSH access. Allow ADB to run on the device by configuring SSH port forwarding.ssh kristi@10.129.198.246 -p 2222 -L 5555:localhost:5555https://blogger.googleus[...]

___________________________
@hacking_Attack
@Hacking_Video

ercontent.com/img/a/AVvXsEhsYeDNai_E9Y-1Mxs-c3XM6RC9-iI1l-8eRF0pA78pcqHShkHgGQ_yI5zk-8zYItMysNdyhgTZsTaydPkgWJeiOWnmfRniKS4qfJkj9QAD6-bVrSvswEdSRABLlfgejHYmg9MzekhbRbjjw0xpSyFGAvQJr5kawGMkQFSdhcNaiccMd6f2FK8SqmFDtQ=s16000 After configuring port forwarding, I can run ADB commands, obtain a shell, elevate the shell to root, and search for the root.txt file.Note:If you don’t have an ADB installed in your Kali Machine, use the command:apt install adbIn order to connect with adb use the following command:adb connect 127.0.0.1:5555In order to get the shell, execute the command given below, as we have already established a connection.adb -s 127.0.0.1 shell

___________________________
@hacking_Attack
@Hacking_Video

Multiple Vulnerabilities in AWS and Other Major Cloud Services
https://www.reddit.com/r/redteamsec/comments/rbde9d/multiple_vulnerabilities_in_aws_and_other_major/

submitted by /u/GHIDRAdev (https://www.reddit.com/user/GHIDRAdev)
[link] (https://www.sentinelone.com/labs/usb-over-ethernet-multiple-privilege-escalation-vulnerabilities-in-aws-and-other-major-cloud-services/) [comments] (https://www.reddit.com/r/redteamsec/comments/rbde9d/multiple_vulnerabilities_in_aws_and_other_major/)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
How hard is it actually to hack WiFi?

I feel very confused on this topic. Because when I hear stories about people hacking using their neighbours WiFi or something like that, they always make it seem like it is the easiest thing in the world.

And I am just curious as to how easy it would be for a thread actor to hack into a normal house holds WiFi?

submitted by /u/Galaxygon
[link] [comments]
➖ Sent by @TheFeedReaderBot ➖

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Best way to start?

I’m new to this, and I’m trying to figure out how to get started. I am currently working through google Gruyere, and I have very little HTML/JS knowledge, but I know a few other languages. Any resources I should check out or tricks I should try? Thanks!

submitted by /u/Me7474
[link] [comments]
➖ Sent by @TheFeedReaderBot ➖

___________________________
@hacking_Attack
@Hacking_Video

KaliIntelligenceSuite - Shall Aid In The Fast, Autonomous, Central, And Comprehensive Collection Of Intelligence By Executing Standard Penetration Testing Tools
http://www.kitploit.com/2021/12/kaliintelligencesuite-shall-aid-in-fast.html

___________________________
@hacking_Attack
@Hacking_Video

Kali Intelligence Suite (KIS) shall aid in the fast, autonomous, central, and comprehensive collection of intelligence by automatically: executing Kali Linux tools (e.g., dnsrecon, gobuster, hydra, nmap, etc.) querying publicly available APIs (e.g., Censys.io, Haveibeenpwned.com, Hunter.io, Securitytrails.com, DNSdumpster.com, Shodan.io, etc.) storing the collected data in a central rational database (see next section) providing an interface to query and analyze the gathered intelligence After the execution of each Kali Linux tool or querying APIs, KIS analyses the collected information and extracts as well as reports interesting information like newly identified user credentials, hosts/domains, TCP/UDP services, HTTP directories, etc. The extracted information is then internally stored in different PostgreSql database tables, which enables the continuous, structured enhancement and re-use of the collected intelligence by subsequently executed Kali Linux tools.
Additional features are: pre-defined dependencies between Kali Linux tools ensure that relevant information like SNMP default community strings or default credentials (https://www.kitploit.com/search/label/Default%20Credentials) is known to KIS before trying to access the respective services remembering the execution status of each Kali Linux tool and API query ensures that already executed OS commands are not automatically executed again data imports of scan results of external scanners like Masscan, Nessus, or Nmap supporting the intelligence collection based on virtual hosts (vhost) using a modular approach that allows the fast integration of new Kali Linux tools parallel Kali Linux command execution by using a specifiable number of threads enables users to kill Kali commands via the KIS user interface in case they take too long access public APIs to enhance data with OSINT Setup and Installation Refer to INSTALL (https://github.com/chopicalqui/KaliIntelligenceSuite/blob/main/INSTALL.md) for more information. KIS' Data and Collection Model The following figure illustrates KIS' data and collection model. Thereby, each node represents a table in the rational database and each solid line between the nodes documents the corresponding relationship. The dashed directed graphs document based on which already collected intelligence (source node) KIS is able to collect further information (destination node). The labels of the directed graphs (https://www.kitploit.com/search/label/Directed%20Graphs) document the techniques used by KIS to perform the collection.

___________________________
@hacking_Attack
@Hacking_Video

Scoping the Engagement Scoping is an essential feature of KIS, which specifies on which IP networks, IP addresses, host names, etc.,
KIS is allowed to collect data (e.g., via OSINT or active scans) from. Before diving into scoping, it is important to understand the following collection types, which are supported by KIS: Passive: Passive collections do not directly interact with the targets but obtain the information from third-party sources like whois. Per default, KIS automatically executes these collections and, thereby, no scoping is required. Active: Active collections directly interact with the targets by for example actively scanning them. Thus, in contrast to passive collections, these type of collection requires permission from the target's owner and, therefore, KIS does not automatically perform active collections unless the targets are explicitly marked as in scope. Active*: Active* collections are actually passive collections. Nevertheless, as accessing some third-party sources is somehow limited (e.g., querying certain sources like Shodan.io cost credits), they are treated like active collectors, and, as a result, targets must be marked as in scope in order to perform active* collections on them. Scopes can be set on the following items by using the script kismanage: IP networks and IP addresses: For IP networks the following scope types can be set: all: Sets the given IP network (e.g., 192.168.1.0/24) together with all IP addresses (e.g., 192.168.1.1) that are within this network range in scope. As a result, KIS automatically executes any active and active* collectors on such IP networks and IP addresses. This scope type is useful during penetration tests where the scope is limited to certain IP networks and all their IP addresses. The following listing provides an example on how this scope type is set during the initial intel collection setup: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the network 192.168.1.0/24 to workspace example and set the scope to all (default)
$ sudo docker-compose run kaliintelsuite kismanage network -w example -a 192.168.1.0/24
# add new IP address 192.168.1.1 to workspace example. IP address is automatically in scope due to the network's scope all
$ sudo docker-compose run kaliintelsuite kismanage host -w example -a 192.168.1.1
# verify the initial setup
$ sudo docker-compose run kaliintelsuite kisreport host -w example --csv | csvcut -c "Network (NW)","Scope (NW)","IP Address (IP)","In Scope (IP)" | csvlook
| Network (NW) | Scope (NW) | IP Address (IP) | "In Scope (IP)" |
| -------------- | ------------- | --------------- | --------------- |
| 192.168.1.0/24 | all | 192.168.1.1 | True | strict: Sets the given IP networks' (e.g., 192.168.1.0/24) scope to strict. In contrast to type all, the network itself is not in scope and IP addresses within this network range (e.g., 192.168.1.1) are not automatically in scope, unless they are explicitly added. As a result, KIS only automatically executes any active or active* collectors on IP addresses that are explicitly added to the scope. This scope type is useful during penetration tests where the scope is limited to certain IP addresses within a given network. The following listing provides an example on how this scope type is set during the initial intel collection setup: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the network 192.168.1.0/24 to workspace example and set the scope to strict
$ sudo docker-compose run kaliintelsuite kismanage network -w example -a 192.168.1.0/24 -s strict
# add new IP address 192.168.1.1 to workspace example and set it in scope (default)
$ sudo docker-compose run kaliintelsuite kismanage host -w example -a 192.168.1.1
# verify the initial setup

___________________________
@hacking_Attack
@Hacking_Video

$ sudo docker-compose run kaliintelsuite kisreport host -w example --csv | csvcut -c "Network (NW)","Scope (NW)","IP Address (IP)","In Scope (IP)" | csvlook
| Network (NW) | Scope (NW) | IP Address (IP) | "In Scope (IP)" |
| -------------- | ------------- | --------------- | --------------- |
| 192.168.1.0/24 | strict | 192.168.1.1 | True | exclude: Sets the given IP network (e.g., 192.168.1.0/24) together with all IP addresses (e.g., 192.168.1.1) that are within this network range out of scope. As a result, KIS does not execute any active and active* collectors on this IP network and its IP addresses. This scope type is the default type for all IP networks and IP addresses that are automatically identified by KIS (e.g., via whois, DNS resolution, etc.). Nevertheless, this scope type can be used to manually exclude networks from scope at a later time. Second-level domain and host names: For second-level domains (e.g., megacorpone.com), the same scope types as for IP networks (see above) exist. Their mode of operation is described below: all: Sets the given second-level domain (e.g., megacorpone.com) together with all sub-domains (e.g. www.megacorpone.com (http://www.megacorpone.com/)) in scope. As a result, KIS automatically executes any active and active* collectors on such host names. This type is useful during penetration tests where the scope is limited to certain second-level domains and all their sub-level domains. The following listing provides an example on how this scope type is set during the initial intel collection setup: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the second-level domain megacorpone.com to workspace example and set the scope to all (default)
$ sudo docker-compose run kaliintelsuite kismanage domain -w example -a megacorpone.com
# add new host names to workspace example. The host names are automatically in scope due to the second-level
# domain's scope all
$ sudo docker-compose run kaliintelsuite kismanage hostname -w example -a www.megacorpone.com ftp.megacorpone.com
# verify the initial setup
$ sudo docker-compose run kaliintelsuite kisreport domain -w example --csv | csvcut -c "Second-Level Domain (SLD)","Scope (SLD)","Host Name (HN)","In Scope (HN)" | csvlook
| Second-Level Domain (SLD) | Scope (SLD) | Host Name (HN) | In Scope (HN) |
| ------------------------- | ----------- | ------------------- | ------------- |
| megacorpone.com | all | megacorpone.com | True |
| megacorpone.com | all | www.megacorpone.com | True |
| megacorpone.com | all | ftp.megacorpone.com | True | strict: Sets the given second-level domains (e.g., megacorpone.com) in scope. In contrast to type all, any sub-level domains (e.g., www.megacorpone.com (http://www.megacorpone.com/)) are not automatically in scope, unless they are explicitly added. As a result, KIS automatically executes any active or active* collectors on such in-scope second-level domains and additionally on those sub-level domains that are explicitly added to the scope. This type is useful during penetration tests where the scope is limited to certain sub-level domains. The following listing provides an example on how this scope type is set during the initial intel collection setup: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the second-level domain megacorpone.com to workspace example and set the scope to strict
$ sudo docker-compose run kaliintelsuite kismanage domain -w example -a megacorpone.com -s strict
# add new host names to workspace example. They are automatically in scope due to kismanage's default value.
$ sudo docker-compose run kaliintelsuite kismanage hostname -w example -a www.megacorpone.com ftp.megacorpone.com
# verify the initial setup

___________________________
@hacking_Attack
@Hacking_Video

$ sudo docker-compose run kaliintelsuite kisreport domain -w example --csv | csvcut -c "Second-Level Domain (SLD)","Scope (SLD)","Host Name (HN)","In Scope (HN)" | csvlook
| Second-Level Domain (SLD) | Scope (SLD) | Host Name (HN) | In Scope (HN) |
| ------------------------- | ----------- | ------------------- | ------------- |
| megacorpone.com | strict | megacorpone.com | False |
| megacorpone.com | strict | www.megacorpone.com | True |
| megacorpone.com | strict | ftp.megacorpone.com | True |
# Note that KIS treats the second-level domain also as a host name. As it has not been explicitly put in scope, it
# is still out of scope. exclude: Sets the given second-level domains (e.g., megacorpone.com) together with all sub-level domains out of scope. As a result, KIS does not execute any active and active* collectors on these second-level domains. This scope type is the default type for all second-level domains and their sub-level domains that are automatically identified by KIS (e.g., via extraction from certificates, etc.). Thus, it is not necessary to explicitly set this scope type. Nevertheless, this scope type can be used to manually exclude second-level domains at a later time. Virtual hosts (vhost): KIS supports scanning vhosts (https://httpd.apache.org/docs/2.4/vhosts/) by using tools like Nikto or Burp Suite Professional (https://www.kitploit.com/search/label/Burp%20Suite%20Professional) (see argument --vhost of script kiscollect. Which vhosts are in scope and which are not is indirectly specified by scoping IP networks and IP addresses (see above) together with Second-level domain and host names (see above). Below are two examples to demonstrate how it works: Example 1: Let's assume the second-level domain google.com together with all sub-level domains that resolve to a network range within 172.217.0.0/16 are in scope. In this case, the top-level domain google.com is added to the KIS database with scope type all as documented below: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the second-level domain google.com to workspace example and set the scope to all (default)
$ sudo docker-compose run kaliintelsuite kismanage domain -w example -a google.com In this case, KIS is able to, among other things, enumerate any sub-level domains as well as resolve their corresponding IP addresses. In addition, to ensure that KIS scans any host with an IP address within the IP network range 172.217.0.0/16, this network range must be added to KIS with scope type all as well: # add the network 172.217.0.0/16 to workspace example and set the scope to all (default)
$ sudo docker-compose run kaliintelsuite kismanage network -w example -a 172.217.0.0/16 Example 2: Let's assume the second-level domain google.com together with all sub-level domains that resolve to any network range are in scope. In this case, the top-level domain google.com is added to the KIS database with scope type all as documented below: # create a new workspace example
$ sudo docker-compose run kaliintelsuite kismanage workspace -a example
# add the second-level domain google.com to workspace example and set the scope to all (default)
$ sudo docker-compose run kaliintelsuite kismanage domain -w example -a google.com In this case, KIS is able to, among other things, enumerate any sub-level domains as well as resolve their corresponding IP addresses. In addition, to ensure that KIS scans any host, the network range 0.0.0.0/0 must be added to KIS with scope type all as well: # add network 0.0.0.0/0 to workspace example and set the scope to all (default)

___________________________
@hacking_Attack
@Hacking_Video