Tuesday, September 25, 2007

2 Factor Authentication Update

I don't believe this, i can't basically do a SQL injection, CSRF or XSS! Everything i wanted to do is basically either encrypted or if i injection a simple character like ", it says service unavailable. This application can be considered very secure it terms of encryption and of good standard if weighing it against the OWASP top ten. Even if i enter a value like 10, this value will be encrypted with this:


I am running outta ideas, tell me what more can i do??

The Hacka Man


Mitmwatcher said...

For reversing 2 factor auth application the things to kept in mind (at least I will keep are )

First Link:
Start looking at the Algorithm level most of the implementation are Time synchronized or Counter Synchronized (rfc 4226)or use S/Key based implementations both need a shared key for authentication Get the method where the shared key stored or obtained

Second Link:

Next part is is the Connection between the AUTH server and the client SSL (I assume it is )
how is the certificate info is stored on client
If it is applet based how is the signing of applet taking place
can you change the rt.jar of JVM (this bug was fixed in new JVMs)to bypass this checking

How does the client react when certificate is replaced by self signed

Third Link :
what is ethereal spitting when the client is connected
Is connection made to any remote server other then the remote AUTH server, Is it HTTP/S
If the algo is home grown check for the crypt functions and Type of RAND functions used in decompiled Jar file do you see any buffer attacks

Hope these help you to start


Anonymous said...

Thanks mitmwatcher, i can say that the algorithm is based on time and session management. Also, when you say get the method where the shared key stored or obtained, what do you actually mean? HTTP GET or POST method or is there some other implication?

For the second link, i will have to verify again. How can i check the signing of applet?

For the third link, the connection is only made to the remote Auth Server and no where else and its HTTPS. I have yet to decompile any jar file. I am still verifying the logic and some other issues. Till i verify that i can't find anything more, i will then proceed to decompile the jar file.


mitmwatcher said...

You cant get the shared secret Key from the headers or JS it might be a server side call or a method embedded in the client applet
check the HOTP rfc in the previous reply for more insights on shared key.
If the applet is running on the cell phone then mostly it is hardware token mostly IMEA number

You can find the certfile in the
use http://blogs.sun.com/andreas/resource/InstallCert.java
to install the new certificate and see how the applet reacts

Decompile the Jar lets see whats inside ;)


Anonymous said...

Can you leave your email down or send me your personal email?


Anonymous said...

myscreen name at gmail

Anonymous said...

send you an email.