Password security

Suppose I have a web form for an internet web application where the application user enters their username and password. When the submit button is pressed the password is sent to the server side code. At that point, isn't my password secure in the sense that no one can view the password in memory? Isn't the password only vulnerable on the client side (Aspx, html) ?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan ChongBusiness Systems Analyst , ex-Senior Application EngineerCommented:
>>At that point, isn't my password secure in the sense that no one can view the password in memory?
that's where we need to have a Secured Sockets Layer (SSL) connection comes into place.

What is SSL ( Secure Sockets Layer)?

What is SSL?

What Is SSL (Secure Sockets Layer) and What Are SSL Certificates?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
madunix (Fadi SODAH)Chief Information Security Officer Commented:
Make sure that
• users assigned unique passwords
• users required to change the passwords on a periodic basis
• passwords should be encrypted and not displayed on the computer screen when entered
• If wrong password is entered a predefined number of times, typically three, the logon ID should be automatically locked out.
HuaMin ChenProblem resolverCommented:
I think there should be no problem, as the relevant password is being encrypted by Web browser as well.
That's only true if https is used ... if the web developer was not that much bright, he could i.e. submitted the password as cleartext in the URL or may hit another security landmine.

To the initial question: The password is as secure as the developer's code treats it. Depending on the laziness of the developer the cleartext of your password could be remain in at least both client's and server's memory (although it's not that easy to retrieve it from there ...), in the respective pagefiles and in some other places. Really dumb developers would store them in clear text to the database. If the developer was clever, he would have implemented the extra code to erase the password's text immediately after generating the needed hash values from it. That is true for both server and client software ...

Besides of that there could be some threats to your password like i.e. keyloggers etc. ...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.