Ghidra quickstart & tutorial: Solving a simple crackme
In this introduction to Ghidra we will solve a simple crackme – without reading any assembly!
The first of several Ghidra tutorials by Ghidra Ninja. Be sure to follow on Twitter!
March 31, 2019
Ghidra quickstart & tutorial: Solving a simple crackme
Comments Off on Ghidra quickstart & tutorial: Solving a simple crackme
March 30, 2019
ARM Assembly Basics
ARM Assembly Basics by Azeria.
Why ARM?:
This tutorial is generally for people who want to learn the basics of ARM assembly. Especially for those of you who are interested in exploit writing on the ARM platform. You might have already noticed that ARM processors are everywhere around you. When I look around me, I can count far more devices that feature an ARM processor in my house than Intel processors. This includes phones, routers, and not to forget the IoT devices that seem to explode in sales these days. That said, the ARM processor has become one of the most widespread CPU cores in the world. Which brings us to the fact that like PCs, IoT devices are susceptible to improper input validation abuse such as buffer overflows. Given the widespread usage of ARM based devices and the potential for misuse, attacks on these devices have become much more common.
Yet, we have more experts specialized in x86 security research than we have for ARM, although ARM assembly language is perhaps the easiest assembly language in widespread use. So, why aren’t more people focusing on ARM? Perhaps because there are more learning resources out there covering exploitation on Intel than there are for ARM. Just think about the great tutorials on Intel x86 Exploit writing by Fuzzy Security or the Corelan Team – Guidelines like these help people interested in this specific area to get practical knowledge and the inspiration to learn beyond what is covered in those tutorials. If you are interested in x86 exploit writing, the Corelan and Fuzzysec tutorials are your perfect starting point. In this tutorial series here, we will focus on assembly basics and exploit writing on ARM.
Written in the best tradition of sharing technical knowledge and skill, this is your ticket to over 100 billion ARM powered devices. Not all of them of interest and/or vulnerable, but out of 100 billion (higher now) you will be kept busy.
Enjoy!
Comments Off on ARM Assembly Basics
March 29, 2019
Pentagon Adopts Hostile Adoption Strategy
Pentagon’s Multibillion-Dollar DEOS Contract is Guaranteed for Microsoft
High-five traffic saturated networks between groups of North Korean, Chinese and Russian hackers when they read:
In the coming weeks, the Pentagon—through its partner, the General Services Administration—will bid out a cloud-based contract for enterprisewide email, calendar and other collaboration tools potentially worth as much as $8 billion over the next decade.
…
Yet former defense officials, contracting analysts and industry experts tell Nextgov the Defense Enterprise Office Solutions contract is one that tech giant Microsoft—with its Office 365 Suite—simply cannot lose.
Yes, the Pentagon, through a variety of bidders, all of who offer Microsoft based solutions, is adopting a hostile adoption strategy, described as:
According to Defense Department spokeswoman Elissa Smith, the intent is for DEOS to replace all the disparate, duplicative collaboration tools Defense Department agencies use around the world. Components, including the Army, Navy and Air Force, “will be required” to use the same cloud-based business tools.
“It is expected that DEOS will be designated as an enterprise solution for DOD-wide adoption and organizations,” Smith told Nextgov. “Components that have already implemented different solutions with similar functionality will be required to migrate to DEOS.”
You may remember how successful the FBI Virtual Case File project was, $170 million in the toilet, where local FBI offices were to be “forced” to migrate to a new system. Complete and utter failure.
Undeterred by previous government IT failures, the Pentagon is upping the stakes 47 X the losses in the FBI Virtual Case File project and, even more importantly, risking national security on hostile adoption of an unwanted product.
If that weren’t bad enough, the Office 365 Suite offers a security single point of failure (SPOF). Once the system is breached for one instance, it has been breached for all. Hackers can now abandon their work on other systems and concentrate on Microsoft alone. (A thanks on their behalf to the Pentagon.)
Hackers are unlikely to take up my suggestion because an eight year slog to complete failure leaves non-Microsoft systems in operation during and past the project’s failure date. Not to mention that a hostile transition to an unwanted system is likely to leave openings for exploitation. Happy hunting!
Comments Off on Pentagon Adopts Hostile Adoption Strategy
March 28, 2019
March 27, 2019
GHIDRA 9.0.1 has been posted
That was quick! Version 9.0.1 of GHIDRA is available for downloading. Release notes.
Comments Off on GHIDRA 9.0.1 has been posted
March 7, 2019
Nearest Neighbor/Fire Hydrant?
HazardHub’s HydrantHub Passes 10 Million Fire Hydrant Locations Nationwide
From the post:
Distance to a fire hydrant is one of the most critical components to properly priced homeowners and property insurance. Yet – too often – hydrant data is simply missing from existing fire protection algorithms. HydrantHub’s aim is to break that data blockage by collecting and standardizing hydrant data, then making that data available to consumers, insurers, inspectors, and municipalities across the country. Not only can HydrantHub tell you the closest hydrant, it can also tell you the number within perimeter 1,000-foot radius of a location, giving insurers unique insight as to how well a community can provide critical water assets to a fire. The hydrant locations in HydrantHub cover over 80% of the US population with hydrants.
HydrantHub is available via HazardHub’s free “Where’s My Closest Hydrant” tool on http://www.hazardhub.com, as well as HazardHub’s powerful API.
Exploring the placement and number of fire hydrants by race and social class is one re-use of this data. Another re-use includes determining when different fires would place conflicting demands on fire hydrants.
Does every data set that admits to a benign use, have one or more non-benign uses? I suspect that to be the case. Counter-examples anyone?
Comments Off on Nearest Neighbor/Fire Hydrant?