Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| CanAlsoBe | Allowed | B | 312 | Cleartext Storage of Sensitive Information |
| ChildOf | Allowed-with-Review | C | 522 | Insufficiently Protected Credentials |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 255 | Credentials Management Errors |
| MemberOf | Prohibited | C | 930 | OWASP Top Ten 2013 Category A2 - Broken Authentication and Session Management |
| MemberOf | Prohibited | C | 963 | SFP Secondary Cluster: Exposed Data |
| MemberOf | Prohibited | C | 1013 | Encrypt Data |
| MemberOf | Prohibited | C | 1028 | OWASP Top Ten 2017 Category A2 - Broken Authentication |
| MemberOf | Prohibited | C | 1346 | OWASP Top Ten 2021 Category A02:2021 - Cryptographic Failures |
| MemberOf | Prohibited | C | 1396 | Comprehensive Categorization: Access Control |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-332 | Gain Privileges or Assume Identity (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1013 | Encrypt Data |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1346 | OWASP Top Ten 2021 Category A02:2021 - Cryptographic Failures |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 255 | Credentials Management Errors |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 963 | SFP Secondary Cluster: Exposed Data |
SSL (Secure Socket Layer) provides data confidentiality and integrity to HTTP. By encrypting HTTP messages, SSL protects from attackers eavesdropping or altering message contents.
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Access Control | N/A | Gain Privileges or Assume Identity | N/A |
Enforce SSL use for the login page or any page used to transmit user credentials or other sensitive information. Even if the entire site does not use SSL, it MUST use SSL for login. Additionally, to help prevent phishing attacks, make sure that SSL serves the login page. SSL allows the user to verify the identity of the server to which they are connecting. If the SSL serves login page, the user can be certain they are talking to the proper end system. A phishing attack would typically redirect a user to a site that does not have a valid trusted server certificate issued from an authorized supplier.
OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
| Reference | Description |
|---|
| Ordinality | Description |
|---|
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
N/A
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| Software Fault Patterns | SFP23 | N/A | Exposed Data |