WCF Misconfiguration: Weak Token

ABSTRACT

若在未經加密的通道上使用 UsernameToken 及明文密碼，則可截取 SOAP 消息的攻擊者會趁機獲取該密碼。

EXPLANATION

使用 UsernameToken 的服務提供程序，可能會接受以明文形式發送的密碼。若通過未經加密的通道發送明文密碼，則可截取 SOAP 消息的攻擊者會趁機獲取該憑證。

下列 WCF 服務提供程序配置使用了此 UsernameToken：

     ...
<security mode="Message">
	 <message clientCredentialType="UserName" />
     ...

REFERENCES

[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) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II, APP3330 CAT I

[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II, APP3330 CAT I

[6] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 254

[7] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Insufficient Authentication

[8] Standards Mapping - FIPS200 - (FISMA) MP

[9] Standards Mapping - SANS Top 25 2010 - (SANS 2010) Porous Defenses - CWE ID 311

[10] Standards Mapping - SANS Top 25 2011 - (SANS Top 25 2011) Porous Defenses - CWE ID 311

[11] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 4.1, Requirement 6.3.1.3, Requirement 6.5.8, Requirement 8.4

[12] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 4.1, Requirement 6.5.3, Requirement 8.4

[13] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 4.1, Requirement 6.5.8, Requirement 8.4

97av