CWE-549 Details

The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.

Einführungsmodi

Implementation

Anwendbare Plattformen

Sprache

Class: Not Language-Specific (Undetermined)

Technologien

Class: Not Technology-Specific (Undetermined)
Class: Web Based (Undetermined)

Häufige Konsequenzen

Mögliche Gegenmaßnahmen

Phases : Implementation // Requirements
Recommendations include requiring all password fields in your web application be masked to prevent other users from seeing this information.

Erkennungsmethoden

Automated Static Analysis

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.)
Wirksamkeit : High

Hinweise zur Schwachstellen-Zuordnung

Begründung : 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.
Kommentar : 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.

Referenzen

REF-44

24 Deadly Sins of Software Security
Michael Howard, David LeBlanc, John Viega.

Einreichung

Änderungen