Broken authentication occurs when the application Miss managers session related information such that
the user's identity will be compromised before deep diving.
We need to talk about what is the session first and what is the session I.D. then how each TTP and session
I.D. are or how does each TTP handle session I.D. first.
If such an idea is unique to each user it is used for only one authenticated session.
It is generated by the server and sent to the client in many forms such as hidden variable.
It can be a cookie or a are L query string and the user is expected to send the same idea upon the next
request.
Now how does each TTP handle session I.D..
Unfortunately HDTV and HDTV s protocols they do not provide tracking of users session.
So typically vendors will provide a built in session tracking methodology or developers will develop
their own approach to handle sessions.
Thus a room for error can occur attackers will take advantage of such bad session management practices
to compromise password keys or authentication tokens.
The aim here is to either get into someone else's session or use a session which has been ended by the
user to steal session related information.
The session is guest.
This is especially useful if the session at hand is for a privileged account.
Some examples on how to steal sessions are pressing the backward button after log out to see if you
can stills view the previous page and access the session itself.
You can try to head the euro out very key after logging out to check if you were able to access the
page check for the presence of session related information in the URL.
Because sometimes developers pass such information and get your real strings and you can as well try
to find some credentials in the source code itself by right clicking on the page and view source.
Sometimes coders.
They just hard code credentials for ease of access.
We can protect our self from broken authentication attacks using various ways such as using long and
complex random session I.D. that cannot be guessed.
It is always recommended to use each s to prevent disclosure of session I.D. using various men in the
middle type of attacks.
Always use secure Cookies make sure this session is timed out on the server.
Consider regenerating a new session upon successful authentication or privilege level change.
New URL query string should not be used for session I.D. because this is easily the Kosovo and always
use or whenever possible use multi factor authentication.