Back Doors Mean Wide-Open Danger


Finding back doors before they're compiled into applications can save time and money


Email    print   
October 16, 2007 —  (Page 1 of 2)
SAN FRANCISCO — Keep your friends close and your hackers closer. Right now, as you read this, it's entirely possible that one of your company's programmers is writing exploitable code into a front-line application. The practice is not uncommon, and both the open source world and internal corporate teams are constantly placed at risk by rogue coders. But finding back doors isn't impossible; tests can detect such code before it can harm deployed software.

Chris Wysopal, CTO and co-founder of Veracode, gave a speech at the IT Security World Conference and Expo here in mid-September, and in it he detailed the numerous methods and reasons for writing back doors. While the methods are diverse and their implementation specific, he explained that the reasons tend to be less ominous: Most hackers who write back doors do so simply because they can. Examples of Open Backdoors

Sometimes, hidden back doors can amount to a signature from a programmer: they're something the coder simply does with all of his or her applications. For the same reason some programmers hoard old manuals and software, others may add back doors into applications simply for the sake of knowing they still control their projects, long after they're complete.

And still other back doors are explicitly used for targeted attacks.

Wysopal showed numerous examples of back doors found in the wild during his talk. The tactics used in these examples, he noted, can be used to help development teams track down such exploits during code audits.

The first and easiest way to find back doors, said Wysopal, is using static analysis. Dynamic analysis requires the actual backdoor code to be in use during analysis, which according to him is quite rare. “You can scan programs for all hashing routines, such as crypto. Go back in the data flow and see what's going into the data routines. If there's any static values going in, that's a flag,” Wysopal explained, adding that this type of activity is indicative of a back door that includes simple hidden login names and passwords.




Pages 1 2 


Share this link: http://sdt.bz/31239
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Industry Watch: RIM needs to get back its mojo
The company’s twin-CEOs are stepping down, but what can the new CEO do to regain its image as a must-have smartphone? Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb