Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
Geowifi - Search WiFi Geolocation Data By BSSID And SSID On Different Public Databases

https://blogger.googleusercontent.com/img/a/AVvXsEgQctqedwnCqwsLTpstL7YNEET5azHKUABoUEkyOIKUkmR1l7zCbHNS9ajEOahjr_5haGZH8pnFXV2qGXTwkNWG6Fdx-1W_kpbJAxNiwhdGF6He4TwmC_39sOpll1h6NghiedDo8RauUDVM6FDs4v_si_tXCjE_YglKiPpuizSm2hijHP0ydRXJGTxZ=w640-h348 Search WiFi geolocation data by BSSID and SSID on different public databases. Databases:* Wigle
* Apple
* OpenWifi
* Milnikov Prerequisites* Python3.
* In order to display emojis on Windows, it is recommended to install the new Windows terminal.
*
⚠️ In order to use the Wigle service it is necessary to obtain an API and configure the utils/API.yamlfile replacing the value of the "wigle_auth" parameter for the "Encoded for use" data provided by Wigle. This is necessary for searching by SSID. Installation Use the package manager pip to install requirements. python3 -m pip install -r requirements.txtUsage usage: geowifi.py [-h] (-s SSID | -b BSSID) [-j] [-m]
optional arguments:
-h, --help Show this help message and exit
-s SSID, --ssid SSID Search by SSID
-b BSSID, --bssid BSSID Search by BSSID
-j, --json Json output
-m, --map Map output
* Search by BSSID: python3 geowifi.py -b BSSID * Search by SSID: python3 geowifi.py -s SSID It is possible to export the results in json format using the -jparameter and show the locations on html map using -m. ️
Map output example
https://blogger.googleusercontent.com/img/a/AVvXsEjJWrVu6EK-KeaTsZubzZFJPiSnj60F9fj2IJmQ-nk8eh0LiQKn0LUqLRqckM9k1UQ5Cx-ZNLk0XHpitJpgC6shJGMp6oVBls8aLyp3qsQw3-oKWQYasjrlmtE0CAISo32hl5OPLCbt8-REePb5rotciZQQL3AZiLgM-L0FSAqrgCzGQRZd7Hm7wSKE=w640-h262
Json output example
{
"data":{
"bssid":"A0:XX:XX:XX:6F:90",
"vendor":"TP-LINK TECHNOLOGIES CO.,LTD.",
"mac_type":"MA-L",
"wigle":{
"lat":00.000908922099,
"lon":00.000945220028
},
"apple":{
"lat":"not_found",
"lon":"not_found"
},
"openwifi":{
"lat":00.000808900099,
"lon":00.000845500028
},
"milnikov":{
"lat":"not_found",
"lon":"not_found"
}
}
}
Mentions * This project uses some of the research and code used at iSniff-GPS.
* Thanks to Micah Hoffman for his attention and answers to my questions.
* Thanks to kennbro for lending me his scrupulous eyes to give me feedback. Download Geowifi

___________________________
@hacking_Attack
@Hacking_Video
Dark Reading: Attacks/Breaches
Zero Trust Can't Stop at the Federal Level

The federal government must step in to help local and state governments implement zero trust.
Hacking Articles Tips Tricks Videos Tutorials
Photo
Kali Linux Tutorials
Http-Desync-Guardian – Analyze HTTP Requests To Minimize Risks Of HTTP Desync Attacks

Http-Desync-Guardian is to Analyze HTTP Requests To Minimize Risks Of HTTP Desync Attacks. HTTP/1.1went through a long evolution since 1991 to 2014:

* HTTP/0.9 – 1991
* HTTP/1.0 – 1996
* HTTP/1.1
* RFC 2068 – 1997
* RFC 2616 – 1999
* RFC 7230 – 2014
This means there is a variety of servers and clients, which might have different views on request boundaries, creating opportunities for desynchronization attacks (a.k.a. HTTP Desync).

It might seem simple to follow the latest RFC recommendations. However, for large scale systems that have been there for a while, it may come with unacceptable availability impact. http_desync_guardianlibrary is designed to analyze HTTP requests to prevent HTTP Desync attacks, balancing security and availability. It classifies requests into different categories and provides recommendations on how each tier should be handled.

It can be used either for raw HTTP request headers or already parsed by an HTTP engine. Consumers may configure logging and metrics collection. Logging is rate limited and all user data is obfuscated.

If you think you might have found a security impacting issue, please follow our Security Notification Process. Priorities

* Uniformity across services is key. This means request classification, logging, and metrics must happen under the hood and with minimally available settings (e.g., such as log file destination).
* Focus on reviewability. The test suite must require no knowledge about the library/programming languages but only about HTTP protocol. So it’s easy to review, contribute, and re-use.
* Security is efficient when it’s easy for users. Our goal is to make integration of the library as simple as possible.
* Ultralight. The overhead must be minimal and impose no tangible tax on request handling (see benchmarks). Supported HTTP versions

The main focus of this library is HTTP/1.1. See tests for all covered cases. Predecessors of HTTP/1.1don’t support connection re-use which limits opportunities for HTTP Desync, however some proxies may upgrade such requests to HTTP/1.1and re-use backend connections, which may allow to craft malicious HTTP/1.0requests. That’s why they are analyzed using the same criteria as HTTP/1.1. For other protocol versions have the following exceptions:

* HTTP/0.9requests are never considered Compliant, but are classified as Acceptable. If any of Content-Length/Transfer-Encoding is present then it’s Ambiguous.
* HTTP/1.0– the presence of Transfer-Encodingmakes a request Ambiguous.
* HTTP/2+is out of scope. But if your proxy downgrades HTTP/2to HTTP/1.1, make sure the outgoing request is analyzed.

See documentation to learn more.

Overview

This page contains request classification tiers and reasons as well as mitigations, with explanations for some non-trivial cases. Request classification http_desync_guardianis a library for analyzing and classifying HTTP/1.x requests to provide customers security balanced with necessity to serve traffic for legacy or proprietary systems (not always RFC compliant).

* Compliant– RFC compliant requests (*)
* Acceptable– non RFC compliant requests, but which do not represent security risks
* Ambiguous– requests that might be treated differently by different HTTP servers and therefore may lead to HTTP Desync issues (and request splitting/smuggling as a possible consequence)
* Severe– either malformed or highly likely crafted to trick HTTP parsers and cause HTTP de-synchr[...]

___________________________
@hacking_Attack
@Hacking_Video