Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 28 guests online
 
Free Business and Tech Magazines and eBooks

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Web Applicationsarrow Flex with Jetty
EH-Net
May 25, 2013, 05:37:20 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Flex with Jetty  (Read 7661 times)
0 Members and 1 Guest are viewing this topic.
awalli6i
Newbie
*
Offline Offline

Posts: 3


View Profile
« on: November 19, 2009, 06:07:54 PM »

Hi all...

I have been asked to have a look at a new webapp that my company is working on. It is built with Flex and runs on the Jetty web server. They want some ideas on how to test the security of the application.

Any advice on what tools to use and where to start!

Thanks heaps

A
Logged
Ketchup
Hero Member
*****
Offline Offline

Posts: 1021



View Profile
« Reply #1 on: November 20, 2009, 07:12:20 AM »

I would think that the same techniques that work for any web server should work for Jetty web server.   Look for default directories and applications that are almost always vulnerable.  Check to see if directories that should be secure, are.  SSL security is another check.   Google searching for "Jetty vulnerability" reveals a few hits that may be interesting.  I am not sure about using automated tools for this though.

This is Adobe Flex, right?   It just builds Adobe Flash apps as far as I know.   With Flash, you can try passive methods.   Put a proxy (burp, tamper data, etc) on your session and see what comes over the wire.   I suppose that any programming is done with Action Script in these applications.  That's not my area at all.  Yet, I would assume that the same principles apply for sanitizing user input. 
Logged

~~~~~~~~~~~~~~
Ketchup
awalli6i
Newbie
*
Offline Offline

Posts: 3


View Profile
« Reply #2 on: November 23, 2009, 05:00:27 PM »

Hey,

Thanks for the reply. The version of Jetty that they are using has the "//" problem that allowed me to view the files that make up the login page. From there I could download the swf file for the front page.

Using a little product from HP called swfscan (http://www.communities.hp.com/securitysoftware/blogs/spilabs/archive/2009/03/20/exposing-flash-application-vulnerabilities-with-swfscan.aspx) to decomplie the swf and view the source code. Found a few little issues with the code and was able to get into the app.

Also ran WebScarab over the site and it found lots of nice little bits of information.

Thanks again for the advice.

A
Logged
UNIX
Hero Member
*****
Offline Offline

Posts: 1235


View Profile
« Reply #3 on: December 03, 2009, 05:19:40 AM »

If you haven't already, also take a look at OWASP which should give you some more ideas on how to audit it.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.685 seconds with 23 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

© 2013 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.