Decompiling Applets to find holes
by Roshen Chandran
| 20 Jun 2005
When pen testing web sites that use applets to enforce business rules, it’s a good idea to decompile the applet and poke around it. Here are some of the things we’ve come across that helped us test the application better:
- Hard coded secrets, passwords, symmetric keys and once even an embedded private key
- Weak “custom encryption” logic that could be reverse engineered easily
- Inadequate input validation logic and the boundary conditions being tested for
- A structured listing of business rules that helped us refine our Threat model
- The “secret handshake” used for authenticating the applet to the servlet
This isn’t rocket science. All it takes is a Java decompiler and a few hours of analysis. We use DJ Decompiler, it’s a graphical interface built over the JAD decompiler for Java.
Plynt provides penetration testing and code review services to clients worldwide. If you are interested, please contact us for a quote. We’ll get back to you within one working day.Add yours.closed for this post.
Monthly Archives
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
- March 2008
- January 2008
- December 2007
- November 2007
- April 2007
- March 2007
- February 2007
- January 2007
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
Syndication
You can read full entries of Palisade Blog using an RSS reader. Use this link —



