Password Leak Analysis
The Simple Mail Transfer Protocol (SMTP) does not have any intrinsic methods of proving the authenticity, integrity, and confidentiality of individual messages. As such, it’s relatively easy for third parties to spoof the source of an email, to intercept and modify authentic email, and to monitor the contents of an email. In fact, anybody may claim to have sent an email from an arbitrary source domain.
Over the decades, multiple additional protocols have been developed in order to address these three basic weaknesses of email. Some serve to prove the identities of users of the email protocol (PGP/GPG or other public key cryptography based on individuals), while others are more focused on proving the authenticity and integrity of any email from a particular domain. In this article, we will explore three protocols of the latter category.
The SPF was developed to let domain owners explicitly state which hosts were allowed to send email from that domain. Email receivers may then use the SPF to ascertain the authenticity of an email by way of one or more Domain Name System (DNS) lookups. However, the SPF does not provide cryptographic assertions as to the authenticity of an email. It consists merely of a set of rules to match host names or IP addresses.
A domain may specify the SPF policies within a DNS
TXT record, which will tend to look something like the following if the domain owner does not host their own mail servers:
"v=spf1 include:spf.protection.outlook.com -all"
Notice, that the SPF policy entry starts with a header that specifies the SPF version (
v=spf1), and is followed by a series of statements (or mechanisms) that specify the policy in left-to-right direction. The SPF recognizes eight such statements, which we’ll look into a bit further down. One of the two we see in the example above,
include, merges another domain’s SPF policy with the owned domain. Its SPF policy is much longer, and itself includes to two other domains recursively. Note, that when specifying the SPF policy, the SPF proposed standard explicitly states that a maximum number of DNS lookups (usually 10) for the verifying party must be enforced. So take care not to nest too many SPF policies.
"v=spf1 ip4:18.104.22.168/26 ip4:22.214.171.124/24 ip4:126.96.36.199/24 ip4:188.8.131.52/24 ip4:184.108.40.206/23 ip4:220.127.116.11/24 ip4:18.104.22.168/24 ip4:22.214.171.124/24 include:spfa.protection.outlook.com -all"
include, SPF also recognizes the statements
all statement is a catch-all statement and should only be used at the end of a policy. The statements
ip6 allow the specification of the IP addresses of hosts that are allowed to send email from the domain in question. The statements
mx allow domain owners to specify a host name whose IP address(es) in the equivalent DNS record (
MX) must match the source address of the email under scrutiny. The
ptr statement requires a two-step DNS lookup (IP address ⇒ domain name ⇒ IP address) to result in equal IP addresses for a match. And, lastly, the
exists statement requires the specified domain name entry (
A record) exist for a match. The big part here is that the
exist statement allows macro expansions on the side of the verifying party.
The aforementioned statements may each be prefixed with one of the qualifiers
~ “SoftFail”, and
? “Neutral”, which change what qualifies as a match to the following statement. The qualifier
- will cause the email to be refused completely upon rule match. The qualifier
~ will recommend to the evaluating party that an email is accepted, but categorized as SPAM. The qualifier
? will issue no recommendation to the evaluating party. If no qualifier is specified,
+ is assumed.
In addition to mechanisms and qualifiers, modifiers may be used to either
redirect (or defer) to the authority of another domain, or to specify an
exp-planation for the denial of an email, which will be relayed to the recipient of the denied email. The latter modifier also allows macro expansions.
While the SPF does not provide cryptographic guarantees for the authenticity of email, DKIM does so by signing every legitimate outgoing email with a private key defined by the domain owner. In order to work, DKIM relies on two things: first, a DNS
TXT record that will contain the public key for DKIM email validation, obtained from a DNS
TXT record lookup of a name of the form
"v=DKIM1; k=rsa; p=[Base64-encoded public key]"
Second, every authentic email sent by the domain in question will contain the header
Dkim-Signature. Its value will contain at least 8 parameters that serve to specify the DKIM protocol version, the signature algorithm, what parts of the email were included in the signature, the aforementioned selector and domain to be queried for the DKIM public key, as well as the Base64-encoded cryptographic signature.
Thus, the DKIM protocol will allow email recipients’ servers to verify the authenticity and integrity of the signed parts of an email (note, that the body is not always signed). But because the DKIM protocol cannot be enforced, it does not protect against fraudulent email, and as such, the DKIM protocol should be used at least in conjunction with the SPF.
The DMARC protocol builds upon the SPF and DKIM by introducing the ability to monitor a domain for illegitimate email. In order for DMARC to work, both the SPF and DKIM must be set up. Akin to the SPF and DKIM, DMARC uses the DNS
TXT record of the DNS name
_dmarc.example.com to specify its policy:
Apart from the protocol and version parameter, DMARC defines ten parameters in total. The parameter
p specifies the policy for the domain with one of three values
reject, which have similar functions to the SPF qualifiers
-. Specifying this parameter is necessary for DMARC to function. The parameter
sp allows setting a distinct policy for subdomains. The parameters
aspf allows changing how email from subdomains is treated when the DKIM or SPF policies were issued only for the organizational domain. The parameters
ruf specify where the DMARC reports should be sent to. The former address will receive aggregate reports, while the latter will receive detailed reports for each DMARC validation failure. The parameters
ri allow the fine-tuning of the behavior of the DMARC policy. Note too, that the parameters
pct can be changed to allow domain owners to gradually enforce the DMARC policy.
Let our Red Team conduct a professional social engineering test!
Our experts will get in contact with you!
Further articles available here