hacking: security in practice
Kismet, but for cellular/mobile networks?

(If there's a better subreddit for this, lemme know.)

Basically, title is what I'm looking for. If you've used Kismet, except instead of Wi-Fi, LTE. List of of active base stations / towers, signal strength, operator - Pretty much any and all telemetry that's to be had. Kismet for the 802.11 world has this in spades. But I've yet to find any kind of tool that does this for 3/4/5G. (List of attached peers/handsets would be amazing, but I'd consider it luxury, if its even possible.) Any suggestions on tools or tips would be greatly appreciated.

Perhaps COTS products (pricey tho), or an SDR solution, or perhaps this could be done with mobile chipset API's / via AT commands.. I just don't know and frankly, there's not a lot of info around for something like this. Thanks all for any helpful replies !!!

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

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Could AI create a vulnerability for hashing algorithms?

Hear me out. If we accept that math is a representation of the physical world, then all equations are a representation of physical shape.

AI starts with randomness, and builds an equation to fill a void. The equation forms a shape in the neural network that molds to an external shape, outside the network.

So, it's only logical that an AI could learn the shape of a hashing algorithm, and output values which could trigger a given solution.

At least, that's my thinking. Especially if one kept feeding it random data.

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

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
How do I figure about the archive type / compression scheme of an unknown file?

Hi, given that reading a lot of small files has a huge performance drop, video game files are archived using the best available archive type (and maybe compressed it too). But we all know, even though, apps such as 7-zip give the unknown archive type error, for all we know it's just a deflate archive just like zip.

They change the beginning of file and maybe tinker with it a little, but they almost never go out of their way and write a new archive type.

So by analyzing and de-assambing the file with tools like ghidra and such (if any), how does one figure out what the type of an unknown archive is and whether is it using a compression scheme?

if only I knew the trick behind it...

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

___________________________
@hacking_Attack
@Hacking_Video

Dark Reading: Attacks/Breaches
Ransomware Operators Are Feeling the Heat

Ransomware has maintained its dominance the past few years; however, increased law enforcement attention may result in changes to how it looks in the future.

___________________________
@hacking_Attack
@Hacking_Video

Journey for finding the CSRF Bug lead to the finding of the 403 Forbidden error

Hello myself Manan Aggarwal and this is my First Blog Post that while I was finding the CSRF Bug that Lead to the finding of the 403…Continue reading on Medium »
Read more...

Registrations Open for IWCON 2022 — the Online Infosec Conference & Networking Event
https://infosecwriteups.com/registrations-open-for-iwcon-2022-the-online-infosec-conference-networking-event-41a1b0182b00?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Listen to 15+ awesome speakers and meet some of the coolest peeps in Infosec!Continue reading on InfoSec Write-ups » (https://infosecwriteups.com/registrations-open-for-iwcon-2022-the-online-infosec-conference-networking-event-41a1b0182b00?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Journey for finding the CSRF Bug lead to the finding of the 403 Forbidden error
https://medium.com/@mananaggarwal2001/journey-for-finding-the-csrf-bug-lead-to-the-finding-of-the-403-forbidden-error-a37786b76538?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Hello myself Manan Aggarwal and this is my First Blog Post that while I was finding the CSRF Bug that Lead to the finding of the 403…Continue reading on Medium » (https://medium.com/@mananaggarwal2001/journey-for-finding-the-csrf-bug-lead-to-the-finding-of-the-403-forbidden-error-a37786b76538?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Hack into Skynet —  Real World CTF (2022) walkthrough
https://infosecwriteups.com/hack-into-skynet-real-world-ctf-2022-walkthrough-eb0e3908d9a7?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Continue reading on InfoSec Write-ups » (https://infosecwriteups.com/hack-into-skynet-real-world-ctf-2022-walkthrough-eb0e3908d9a7?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Kali Linux Tutorials
How to Make Your Software Lifecycle Development Process Secure?

It’s important to have a carefully managed and supervised software development lifecycle or SDLC. Applying key, oftentimes small, and practical policies and regulations to each phase of your secure software development lifecycle will allow you and your team to quickly spot issues before they get out of hand — before they manifest in their entirety, take roots and derail your train. Let’s investigate what a software development lifecycle is, how SDLC works, and what it normally includes. Fair warning, each team is different and each product is unique so some life cycles might differ, nevertheless, we’re going to discuss the baseline blueprint most companies take into consideration. What is the software development lifecycle? The truth is that when it comes to building, launching, and updating/maintaining functional software, most businesses have it down to a T. A well-oiled machine that considers just about everything and has everything on schedule. The hiccups present themselves the minute those businesses start to test that very same software. Why? Most developers think of risk management as an interference, a bother that cools their jets — that makes them rework their codes, that forbids them from adding new features, that stalls their creative output.

Software development lifecycle SDLC might very well be a bit of a bore, and not as attractive as creating revolutionary avant-garde tech, but it’s critical because it allows your software to take flight. Secure software development lifecycle (SDLC) is the framework for most of the process behind building an application — from inception point to updates. It takes into account the building, testing, coding, release, deployment, monitoring, and updates. Software development lifecycle SDLC Let’s talk about the phases and why it’s better to implement changes and fix them during these early stages of your software’s lifecycle. The quicker you spot the potential problem the faster you can fix it and the less it will cost you.

* Inception: this phase includes planning and resource audits. It’s a rough draft phase and risk to the overall project – whether it’s doable or not and if so what problems it will face – are taken into account.
* Design and Development: this is when designers take into account possible risks and list potential solutions as well as how said risk will affect the project in the long run.
* Implementation: This phase of the software development lifecycle or SDLC includes the creation of functional software and system configuration. Here your system is fireproofed against the risk previously identified to see if the solutions worked. Also, new risks or bugs may arise.
* Maintenance: this includes debugging and updating once the implementation phase has been completed.
* Audit: the final stage. During this phase in SDLC, risk managers assess if further refinements might be needed, if the changes to the project were substantial and if the project – with the bugs it still might have – is ready for launch. In other words, they balance the cost of postponing the launch date or further development, against the cost of further refinements to the software. How to make your software development lifecycle process secure against risksHere are a few tips on how to properly secure your software lifecycle development process, practices that will help you mitigate risks and fix bugs promptly. architecture risk analysisFrom the get-go, you must understand every aspect of your project. In many cases, while creating the initial blueprint, huge potential risks will rear their heads. Hiccups like requirements, the fact that you might need better coders, design issues, outsourcing problems, etc. Code reviewReview your code ever[...]

___________________________
@hacking_Attack
@Hacking_Video

y time a new line is implemented. Not only that, but supervise just about everything before it’s given the all-clear. Have failsafe and firewalls as well as redundancy in place. That means implementing multiple coders, multiple proofreaders, and even AI-assisted software. penetration testingTest your software constantly. Deep and for a long time. Not just doodle with it but take it through the wringer. Have multiple tests in multiple situations with multiple testers. threat modelingGet advice from other corporations that have gone down the same road you’re starting on. In many cases, the threats that they encountered are the same ones that might blindsight you. They will give you case studies that might mirror your situation. team trainingPro-tip, train your team. Your current project manager might be a wonder when it comes to what they are doing in the present, but softer creation might be too overwhelming, too left field for them. It’s important to have a team that’s trained on what they will experience and how to face those hiccups. In many cases bugs might be frustrating and might demoralize teams and bring down productivity levels — it’s important to have a team that is psychologically trained for SDLC. Why apply security measures to all phases of a software development lifecycle?Because of cost.

In the relative past, most organizations only performed security-related activities, tweaking issues and overseeing if one flew under the radar, in the testing phase. This was the go-to way of doing things. As a result, they would spot bugs, flaws, and other gremlins in the system late in the game. This oftentimes would mean one of two things. Either the software would be released as is, with a series of patches slowly trickling into consumer’s hands as “updates.” Or the corporation would backtrack and try to fix the problem, in many cases working against the clock, missing launch dates, and having to pay exorbitant expenses – like extra hours to staff members – out of their pocket. It was time-consuming and far more expensive. Benefits of making your SLDC process secureThe Systems Science Institute at IBM reported that a punch to the gut, at the testing stage, could end up costing a business 6x more than if they had uncovered glitches during coding or design. Most of those glitches, in many cases, were foreseeable, the same study revealed. Not only that, most of those glitches had been previously identified by someone – either a coder or project manager – and due to a lack of framework had not been addressed. Adding insult to injury, the costs of fixing a bug at such a late stage could end up costing a company 15x.

In the end, implementing a software development lifecycle management will end up saving you money, headaches and will streamline your operation, boosting your chances of success.

___________________________
@hacking_Attack
@Hacking_Video

Http2Smugl - Tool to detect and exploit HTTP request smuggling in cases it can be achieved via HTTP/2 -> HTTP/1.1 conversion
http://www.kitploit.com/2022/01/http2smugl-tool-to-detect-and-exploit.html

___________________________
@hacking_Attack
@Hacking_Video

This tool helps to detect and exploit HTTP request smuggling in cases it can be achieved via HTTP/2 -> HTTP/1.1 conversion by the frontend server. The scheme is as follows: An attacker sends a crafted HTTP/2 request to the target server, which we call frontend. The request is (presumably) converted to HTTP/1.1 and transmitted to another, backend server. The attacker wants to find such a request that it will be seen as two separate requests by the backend server. If the frontend<->backend HTTP/1.1 connection uses keep-alive, the frontend might send requests from other users to the same connection. If we're able to "poison" the connection by a partial request that comes after a legit one, we can retrieve the request from another user. Other possible scenarios include bypassing frontend server protection and rewrites, cache poisoning or cache deception. For more information on the HTTP Request Smuggling, please refer to Portswigger Web Security Academy (https://portswigger.net/web-security/request-smuggling).
Why focus on HTTP/2? In HTTP/2, all HTTP headers' names and values are binary. That means that technically they can contain additional spaces or even newlines. RFC7540#10.3 (https://tools.ietf.org/html/rfc7540#section-10.3) states that implementations that translate HTTP/2 requests to HTTP/1 must take care of the limitations on the character set that arise from such a conversion; most implementations indeed reject them. Despite this, we hope to find ones that allow such headers. They will corrupt the converted HTTP/1.1 request to the backend. Another point is that some recent fixes related to HTTP Request Smuggling might be implemented only for HTTP/1.1 parsers. In general, we hope that there are implementations of HTTP/2 that are not very aware of recent research on HTTP Request Smuggling in HTTP/1.1 and do not include corresponding mitigations. Have you found a single vulnerability (https://www.kitploit.com/search/label/Vulnerability) with this? Surprisingly, yes! I've found a possibility to smuggle a header with a space character through Cloudflare, thus opening a door for Cloudflare<->client smuggling (in case the software of a Cloudflare client accepts & trims header names). Here's the blog post (https://lab.wallarm.com/cloudflare-fixed-an-http-2-smuggling-vulnerability/). There is also another bug bounty report that is not public yet. It makes use of the fact that custom software doesn't filter out newlines in HTTP2 headers, and the smuggling 100% happens (I can see other users' requests). However, I understand that this type of vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) must be frustratingly rare: unlike HTTP/1.1, there are not so many HTTP/2 implementations, and most of them are made with security in mind, thus rejecting suspicious or invalid headers. Detection algorithm The tool has a subcommand that tries to detect if a target vulnerable to the HTTP Request Smuggling attack automatically. The algorithm behind this feature is described in this section. To perform an HTTP Request Smuggling attack, we actually need to "smuggle" a single header first (either Content-Length or Transfer-Encoding). It means that we need to send a header that a) controls where the request body finishes and b) is not processed by the frontend but is processed by the backend. That is usually achieved by modifying a header in some way: adding spaces or tabs at the end of its name, replacing the value with a semi-equivalent etc. The vulnerability detection (https://www.kitploit.com/search/label/Vulnerability%20Detection) algorithm's basic idea is to detect if the server actually processes a smuggled header as if it were Content-Length or Transfer-Encoding. We do this by sending multiple requests: some with valid and others with invalid values for the header. Then try to detect if there's a way to distinguish the responses from these two groups. That is why tool output does not contain

___________________________
@hacking_Attack
@Hacking_Video