835
References
[REF-62]Mark Dowd, John McDonald and Justin Schuh. "The Art of Software Security
Assessment". 1st Edition. 2006. Addison Wesley.
[REF-962]Object Management Group (OMG). "Automated Source Code Security Measure
(ASCSM)". 2016 January. < http://www.omg.org/spec/ASCSM/1.0/ >.
CWE-836: Use of Password Hash Instead of Password for Authentication
Weakness ID : 836
Structure : Simple
Abstraction : Base
Description
The product records password hashes in a data store, receives a hash of a password from a client,
and compares the supplied hash to the hash obtained from the data store.
Extended Description
Some authentication mechanisms rely on the client to generate the hash for a password, possibly
to reduce load on the server or avoid sending the password across the network. However, when
the client is used to generate the hash, an attacker can bypass the authentication by obtaining
a copy of the hash, e.g. by using SQL injection to compromise a database of authentication
credentials, or by exploiting an information exposure. The attacker could then use a modified client
to replay the stolen hash without having knowledge of the original password.
As a result, the server-side comparison against a client-side hash does not provide any more
security than the use of passwords without hashing.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
CWE Version 4.14
CWE-837: Improper Enforcement of a Single, Unique Action
CWE-837: Improper Enforcement of a Single, Unique Action