Vulnerability Note VU#268267
DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust
DomainKeys Identified Mail (DKIM) Verifiers may inappropriately convey message trust when messages are signed using keys that are too weak (< 1024 bits) or that are marked as test keys.
RFC 6376 states "DomainKeys Identified Mail (DKIM) permits a person, role, or organization to claim some responsibility for a message by associating a domain name [RFC1034] with the message [RFC5322], which they are authorized to use. This can be an author's organization, an operational relay, or one of their agents. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. A message can contain multiple signatures, from the same or different organizations involved with the message."
1) CWE-347: Improper Verification of Cryptographic Signature: DKIM information is conveyed in an email header called a DKIM-Signature header field. A Signer can indicate that a domain is testing DKIM by setting the DKIM Selector Flag (t=) flag to t=y. Some verifiers accept DKIM messages in testing mode when the messages should be treated as if they were not DKIM signed. From RFC 6376:
t= Flags, represented as a colon-separated list of names (plain- text; OPTIONAL, default is no flags set). Unrecognized flags MUST be ignored. The defined flags are as follows: y This domain is testing DKIM. Verifiers MUST NOT treat messages from Signers in testing mode differently from unsigned email, even should the signature fail to verify.
A DKIM-compliant email client, including web-based clients, should not convey any DKIM-related trust to the user about messages in testing mode.
2) CWE-326: Inadequate Encryption Strength: DKIM signing keys with fewer than 1024 bits are weak. From RFC 6376:
Since short RSA keys more easily succumb to off-line attacks, Signers MUST use RSA keys of at least 1024 bits for long-lived keys.
It is possible that an attacker could factor the encryption key for a domain that is using DKIM allowing them to sign emails originating from that domain. An attacker may be able to use a test signing key that is treated as trusted.
System administrators should replace all RSA signing keys fewer that 1024 bits and configure their systems to not use or allow testing mode on production servers.
Vendor Information (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Affected||22 Aug 2012||23 Oct 2012|
|Microsoft Corporation||Affected||22 Aug 2012||23 Oct 2012|
|Yahoo, Inc.||Affected||22 Aug 2012||23 Oct 2012|
|Bluehost||Unknown||-||11 Mar 2016|
|Yandex||Unknown||-||15 Mar 2016|
CVSS Metrics (Learn More)
Thanks to Zachary Harris for reporting this vulnerability.
This document was written by Michael Orlando.
- CVE IDs: Unknown
- Date Public: 23 Oct 2012
- Date First Published: 24 Oct 2012
- Date Last Updated: 15 Mar 2016
- Document Revision: 45
If you have feedback, comments, or additional information about this vulnerability, please send us email.