Tom: /* Problem */

2022-12-17T19:23:30Z

‎Problem

Tom: Created page with "==Full Title or Meme== A password should never be stored in plain text. or it can be copied out and used by an attacker. ==Context== * Many providers store passwords locally..."

2022-08-12T22:00:19Z

Created page with "==Full Title or Meme== A password should never be stored in plain text. or it can be copied out and used by an attacker. ==Context== * Many providers store passwords locally..."

New page

==Full Title or Meme==
A password should never be stored in plain text. or it can be copied out and used by an attacker.

==Context==
* Many providers store passwords locally by hashing the password used a secret number as a "salt" for the hashing algorithm.
* One example of a system using stored passwords is Microsoft AD.
* The concept is that the password is not stored in the prover, so it cannot be stolen from the provider.

==Problem==
* If the password hash is taken from a provider, it can be used to sign-into that provider.
* In one well-known attack against air-gapped systems, many users had the same password in providers on both sides of the gap. So if (1) the password hash could be obtained in one side of the gap, and (2) the same AD hash was used on both sides of the gap, then anyone with privileged access on one side could access the other side using the same hash.

==Attacks==
* [https://www.theregister.com/2022/08/08/slack_passwords/?utm_source=daily&utm_medium=newsletter&utm_content=article Slack leaked hashed passwords from its servers for years]

==References==

[[Category: Vulnerability]]

@@ Line 10: / Line 10: @@
 * If the password hash is taken from a provider, it can be used to sign-into that provider.
 * In one well-known attack against air-gapped systems, many users had the same password in providers on both sides of the gap. So if (1) the password hash could be obtained in one side of the gap, and (2) the same AD hash was used on both sides of the gap, then anyone with privileged access on one side could access the other side using the same hash.
+* Hashes need to be upgraded as technology moves forward.  [https://www.nist.gov/news-events/news/2022/12/nist-retires-sha-1-cryptographic-algorithm NIST had deprecated SHA-1] so it should no longer be used for security solutions, like the hashing of secrets.
 ==Attacks==

Hashed Password - Revision history

Tom: /* Problem */

Tom: Created page with "==Full Title or Meme== A password should never be stored in plain text. or it can be copied out and used by an attacker. ==Context== * Many providers store passwords locally..."