Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
public:papers:ifipsec2021 [2021-03-26 11:14] – x242168 | public:papers:ifipsec2021 [2021-08-16 12:44] – x242168 | ||
---|---|---|---|
Line 6: | Line 6: | ||
<TEXT size=" | <TEXT size=" | ||
- | \_{{fa> | + | \_{{fa> |
{{fa> | {{fa> | ||
Line 12: | Line 12: | ||
{{fa> | {{fa> | ||
- | \_{{fa> | + | \_{{fa> |
</ | </ | ||
</ | </ | ||
Line 19: | Line 19: | ||
<TEXT align=" | <TEXT align=" | ||
/* <popover trigger=" | /* <popover trigger=" | ||
- | <button type=" | + | <button type=" |
/* </ | /* </ | ||
\_ | \_ | ||
Line 33: | Line 33: | ||
Title = {How Do Users Chain Email Accounts Together?}, | Title = {How Do Users Chain Email Accounts Together?}, | ||
Author | Author | ||
- | BookTitle | + | BookTitle |
Pages = {}, | Pages = {}, | ||
Publisher | Publisher | ||
Line 46: | Line 46: | ||
Recovery connections between email accounts can be exploited in manual hijacking attacks as has been shown in several incidents during the last years. Yet little is known about users' practices of chaining email accounts together. We conducted a qualitative interview study with 23 students in which they shared their email recovery and forwarding settings with us. Altogether, we collected and analyzed information about 138 different email accounts. We used this data to map email account topologies and analyzed these topologies for recurring patterns. We found that users often make poor configuration decisions in their email recovery setups, and often create patterns in their email recovery topologies that result in security vulnerabilities. Patterns such as loops (seen in more than a quarter of our topologies) could be easily exploited in a targeted attack. We conclude that users need better guidance about how to use email based recovery settings in a robust way. | Recovery connections between email accounts can be exploited in manual hijacking attacks as has been shown in several incidents during the last years. Yet little is known about users' practices of chaining email accounts together. We conducted a qualitative interview study with 23 students in which they shared their email recovery and forwarding settings with us. Altogether, we collected and analyzed information about 138 different email accounts. We used this data to map email account topologies and analyzed these topologies for recurring patterns. We found that users often make poor configuration decisions in their email recovery setups, and often create patterns in their email recovery topologies that result in security vulnerabilities. Patterns such as loops (seen in more than a quarter of our topologies) could be easily exploited in a targeted attack. We conclude that users need better guidance about how to use email based recovery settings in a robust way. | ||
</ | </ | ||
+ | |||
+ | ===== Selected conclusions ===== | ||
+ | |||
+ | * Our results show that email account topologies are diverse, but that many include elements of line and loop topologies. | ||
+ | * Loop topologies are especially concerning, as they allow attackers who already have access to one account to easily gain access to a further account. | ||
+ | * We also found that users created other vulnerabilities in their topologies by placing the final recovery nodes in inaccessible accounts, or by using accounts owned by somebody else as a recovery option. | ||
+ | * Users also tended to keep accounts with physical recovery options (which could be strong recovery options) separate from the rest of the recovery topology. | ||
+ | * Participants were often unaware of the connections between their accounts and only realized during the study that there are recovery links they are not happy with. | ||
+ | |||
+ | ===== Research artifacts (supplementary material) ===== | ||
+ | |||
+ | <button type=" | ||
+ | |||