Hacking Team Breach Leaks Zero-Days, Renews Fight To Regulate Cyberweapons
Patrick O'Neill writes: In the days following a massive hack that confirmed Hacking Team's dealings with repressive regimes around the world, experts are wondering once again how to stop Western technology companies from equipping certain governments with weapons meant to attack journalists, human rights activists, and ordinary civilians. Regulation's backers say that "this is an industry that has failed to police itself," ACLU's Christopher Soghoian argued, but many including the EFF warn that overly broad legislation would harm more than help. In addition, wiredmikey points out that a number of exploits have been released in the wake of the hacking: Several exploits have been discovered, including ones for zero-day vulnerabilities, in the hundreds of gigabytes of data stolen by a hacker from the systems of surveillance software maker Hacking Team. Researchers at Trend Micro analyzed the leaked data and uncovered several exploits, including two zero-days for Adobe Flash Player. A readme document found alongside proof-of-concept (PoC) code for one of the Flash Player zero-days describes the vulnerability as "the most beautiful Flash bug for the last four years since CVE-2010-2161." In addition to the Flash Player exploits, researchers spotted an exploit for a Windows kernel vulnerability, a flaw that fortunately has already been patched. Adobe told SecurityWeek that it's aware of the reports and expects to release a patch on Wednesday.
The usual Statism vs. Libertarianism argument. Whichever side you are on, dear reader, you must be consistent: you can not oppose "regulation" of security researchers while, at the same time, supporting "common sense limits" on gun-ownership, for example.
In Soviet Washington the swamp drains you.
experts are wondering once again how to stop Western technology companies from equipping certain governments with weapons meant to attack journalists, human rights activists, and ordinary civilians.
Are their any governments left that DON'T do this as a matter of practice?
SJW's don't eliminate discrimination. They just expropriate it for themselves.
You can use open-source software, in which security is truly a matter of public accountability.
These companies are essentially arms dealers. Why aren't they regulated? Why are there no export controls on their products? When PGP first came out it was treated as a weapon by the US government because it protected people's digital communications. Now there are companies selling products specifically designed to gain illegal control of other people's computers and monitor their communications and it's perfectly ok? When governments break their own laws they encourage lawlessness. That is the situation we are in today.
butthurt errywear
This is yet another example why we need to ignore the authorities and form our own communications, encryption and Internet.
Internet 3 needs to be...
A mesh network, so individual companies and governments can't control it.
All communications need to be encrypted.
without any dependence or need of DNS.
Without a need for ICANN or any other registration entity.
Developed by everybody.
There are laws against the use of virusses, exploits, or any other method as a mean to get unauthorized accesses to computers.
"Hacking Team" is then provably a bunch of criminals, which should face justice.
First, the entire idea of cyberweapons is laughable. Exploits are only possible because of flaws in the code. That is no more a weapon than an unlocked door.
Second, you cannot regulate them as they are immaterial. It would be possible to discover a previously unknown vulnerability, and then not record the finding anywhere. Congratulations, you have a cyberweapon in your brain. Good luck regulating that.
Like the Subject says... What happened to Slashdot Firehose?
http://slashdot.org/firehose is 404
So, who, effectively, is going to regulate them? They'll just find a place where the regulatory regime will permit (if not actively encourage) their activities. The regulation argument is hilarious.
Help save the critically endangered Blue Iguana
What fight to regulate cyberweapons? What cyberweapons? Jesus are people really that nuts now?
This is my sig. There are many like it, but this one is mine.
Regulation's backers say that "this is an industry that has failed to police itself,"
Would you expect liquor stores to self-regulate and decide the drinking age is too low?
Self-regulation might work for some cheap and easy things, but no industry is going to refuse to sell to a massive portion of the market voluntarily. If you want to stop them you need legal enforcement.
I stole this Sig
ahem, agenda much?
They were basically selling zero day exploits in pre-packaged kits to anyone with money. So... is that legal? Because it sounds like a winner.
Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
Is it just me or does Adobe's software have the worst engineering practices practices in the industry. Every other fucking week there's an Adobe vulnerability. Scratch your ass, Adobe Vulnerability. Sneeze? Adobe Vulnerability. Walk your dog? Adobe Vulnerability.
This company needs to just be banned from producing any software, period, unless they provide the source code as well.
Harrison's Postulate - "For every action there is an equal and opposite criticism"
In a leaked Whatsapp conversation, HT systems and security manager Christian Pozzi complained in April 2015 to a friend that he was growing "bored" at work and his boss, noticing this, was going to assign him "something to do" as an alternative to chatting and playing fantasy soccer games. Pozzi is also known for his wide use of passwords such as "Passw0rd". A truly gifted security manager, I must say.
The key difference is that if you spend an hour sorting out your credit card you continue to live the rest of your life afterwards with few ill effects.
Steve Jobs persuaded an engineer to reduce boot time lower than the engineer though possible by making the equivalence argument. It goes something like this:
Average human life expectancy is 71 years.
Humans are on average conscious for 16 hours per day.
Doing the math, this means you would only have to force 414,915 people to spend an hour "sorting out their credit card" before you've effectively done the equivalent time-damage of killing someone.
There are laws in the United States that makes computer hacking illegal. Corporations suffering losses to attacks with these tools are used should sue for damages.
1. Did Hacking Team realize and develop all their own exploits or is any of it 3rd-party?
2. Does Hacking Team surreptitiously gain the fruits of their clients' labor 'by proxy'?
3. Is the person(s) that hacked Hacking Team excluding some serious things from the data release?
News: New Adobe Flash plugin released!
Response: Sorry guys, closed some backdoors... I mean remote exploitable vulns!
#
News: New Adobe Flash plugin released!
Response: Sorry guys, closed some additional backdoors... I mean remote exploitable vulns!
#
News: New Adobe Flash plugin released!
Response: Hey guys, closed some additional backdoors... I mean remote exploitable vulns!
#
Because who fucking audits their code? I can only imagine what is slipped in under the radar between the rapid version releases.
The real problem here is willingness to fund what is necessary - refactoring all code used in critical systems to ensure they are secure - and to maintain that approach over time in an iterative basis.
We should touch code (at least to review it) - every year - which research indicates is the sweet spot for zero-day exploits. We get more benefits if we refactor the code - effectively resetting the clock for exploit writers to find a new zero day, and develop applications to exploit it.
Working in IT today, I can tell you from experience no one is willing to spend money to constantly refactor code without delivering new functionality (read 'revenue generating functionality'). This approach also is counterintuitive to software engineers trained to value code reuse over rewriting or building new solutions.
Instead, they focus on cosmetic bandaids - such as firewalls, antivirus, patch updates, and policy management. All of these things are important - but in the scheme of things will not stop a zero day exploit - particularly given that most patches for zero days are not available until the zero day is discovered - and then the time it takes the developer/company in question to put out a fix - on average 6 months to a year after the zero day is discovered and reported. Meanwhile the network is wide open to anyone who has figured it out (which is roughly 6 months to a year after a new piece of software is deployed on the network). The problem is related more to how humans learn systems than any particular coding practice. Your code refactor efforts just need to fall inside of that curve - leading rather than following.
Finally - the proposed fixes, such as more regulations, will not fix the problem - and will only serve to drive people out of the business, at the precise time when we need more developers than ever to address the problem effectively.
Steps:
1. Pay for what is needed in IT instead of being cheap. If you get more specific regulation of this - you might not have a choice (e.g. Sarbanes-Oxley)
2. Let your developers as a whole spend some time on evaluating code - the more eyeballs you have the better.
3. Move away from expensive water-fall projects to more flexible agile methods, and adjust your funding protocols to match.
Lodragan Draoidh
The more you explain it, the more I don't understand it. - Mark Twain
Follow the facts to the obvious conclusion: Adobe is being *paid* to add exploits to one of the most ubiquitous pieces of software on the net - tellingly even a requirement for some banking and bill paying sites. Given this seemingly endless fountain of suck, the only logical answer: Adobe is an NSA shop.
I'd agree this makes some sense if you assume that attempts to refactor software do not introduce new chances for bugs/vulnerabilities.
I'd also like to assume that were I to walk by her on the street, Natalie Portman would immediately turn and jump my bones, in front of my wife, who would loudly cheer me on.
I'd argue that its more important that people who chose to code as a profession, are competent in addressing security issues in the design phase. With competent design & practices, it makes the bandaids near irrelevant. A refactor is a way of saying the design stinks.
First, the members of the Hacking Team that knew about the sales to embargoed countries should be prosecuted. Then worry about how to regulate cyber weapons. Otherwise, the most evil of the members (i.e. the ones who knew about the selling to genocidal governments like Sudan) might just go into hiding and offer their services to other evil organizations like the mafia.
See subject: I do put where you spend most of your time online in hosts (favorite sites) @ the TOP of your custom hosts file though - this is IN COMBINATION with DNS!
(OpenDNS specifically since they filter out online threats as I do in my hosts file & they are patched vs. the Kaminsky redirect poisoning flaw here @ home (I never could use them as my DNS with ActiveDirectory networks 'on the job', though)).
Thus, DNS & hosts COMPLIMENT ONE ANOTHER for more speed, security, & reliability online!
(I use DNS for rare sub 4% of the time lookups I have to do, the other 95++% of my time online is spent @ favorite sites in my hosts file, which are verified as correct via REVERSE DNS PINGS in APK Hosts File Engine 9.0++ SR-2 32/64-bit http://start64.com/index.php?o... )
Hardcoding your favorites not only increases speed, + security BUT it also LIGHTENS REMOTE DNS SERVER LOADS too (which DNS admins ought to love actually), & also increases RELIABILITY online vs. redirect poisoned DNS servers (of which 99.999% of ISP dns servers are NOT PATCHED AGAINST mind you), OR vs. "downed" dns servers too!
APK
P.S.=> It's great stuff using hosts & OpenDNS in combination for BOTH added in memory cached speed + reliability too!
However/again - even I don't attempt to put "every site under the sun" into my custom hosts file (the BULK of my file is 3,776,625++ KNOWN BAD SITES or botnet C&C servers, & only ~24 favorite sites currently @ the top of it for BEST resolver speed in RAM)... apk
People are not perfect automatons - therefore you always run the risk, and probably will see new bugs and vulnerabilities. However, that is okay - in the sense that it will still reset the clock (assuming you caught the existing zero days in the process). Now the hackers will have to start over - and it will take them another 6 to 12 months to figure out an exploit to the bugs you introduced - assuming they are actually exploitable. Therefore it makes sense to review and refactor code on a recurring basis. The benefits outweigh the costs.
Lodragan Draoidh
The more you explain it, the more I don't understand it. - Mark Twain
Ensuring all developers in the industry are competent is a pipe dream. Take a look at the most exacting careers you can think of - and you'll find varying levels of competence.
People are imperfect (in the sense that they can have a bad day, and let typos slip by from time to time - even the very best of us). Additionally the real software lifecycle is not like frozen water. It is more like all the different states of water - solid, liquid, and gas, changing as its environment changes on a continuum from birth to death.
I agree we should do something. I think that 'something' should be more than just training and hoping they use what they've learned.
Lodragan Draoidh
The more you explain it, the more I don't understand it. - Mark Twain