Storing a password in plaintext can result in a system compromise.
Password management issues occur when a password is stored in plaintext in an application's properties or configuration file.
Example: The following code reads a password from a properties file and uses the password to connect to a database.
...
01 RECORD.
05 UID PIC X(10).
05 PWD PIC X(10).
...
EXEC CICS
READ
FILE('CFG')
INTO(RECORD)
RIDFLD(ACCTNO)
...
END-EXEC.
EXEC SQL
CONNECT :UID
IDENTIFIED BY :PWD
AT :MYCONN
USING :MYSERVER
END-EXEC.
...
CFG
can read the value of password. If a devious employee has access to this information, they can use it to break into the system.[1] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A7 Insecure Cryptographic Storage
[2] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A8 Insecure Cryptographic Storage
[3] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A8 Insecure Storage
[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3210.1 CAT II, APP3340 CAT I
[5] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 256
[6] Standards Mapping - FIPS200 - (FISMA) IA
[7] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 3.4, Requirement 6.3.1.3, Requirement 6.5.8, Requirement 8.4
[8] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 3.4, Requirement 6.5.3, Requirement 8.4
[9] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 3.4, Requirement 6.5.8, Requirement 8.4