== Description ==

Credential stuffing is the automated injection of breached username/password pairs in order to fraudulently gain access to user accounts. This is a kind of brute force attack: large numbers of spilled credentials are automatically entered into websites until they are potentially matched to an existing account, which the attacker can then hijack for their own purposes.

== Severity ==

Credential stuffing is one of the most common techniques used to take-over user accounts.

== Anatomy of Attack ==

#The attacker acquires spilled usernames and passwords from a website breach or password dump site.
#The attacker uses an account checker to test the stolen credentials against many websites (for instance, social media sites or online marketplaces).
#Successful logins (usually 0.1-0.2% of the total login attempts) allow the attacker to take over the account matching the stolen credentials.
#The attacker drains stolen accounts of stored value, credit card numbers, and other personally identifiable information
#The attacker may also use account information going forward for other nefarious purposes (for example, to send spam or create further transactions)

[[file:Credentialstuffing.png]]

== Risk Factors ==

TBD

== Examples ==

Below are excerpts taken from publications analyzing large-scale breaches. Evidence supports that these breaches were the result of credential stuffing.

*Sony, 2012: “I wish to highlight that two-thirds of users whose data were in both the Sony data set and the Gawker breach earlier this year used the same password for each system.”
**Source: Agile Bits [https://blog.agilebits.com/2011/06/07/two-thirds-of-web-users-re-use-the-same-passwords/]
**Source: Wired [http://www.wired.com/2011/10/93000-sony-accounts-breached/]

*Yahoo, 2013: “What do Sony and Yahoo! have in common? Passwords!”.
**Source: Troy Hunt. [http://www.troyhunt.com/2012/07/what-do-sony-and-yahoo-have-in-common.html]

*Dropbox, 2013: “The usernames and passwords referenced in these articles were stolen from unrelated services, not Dropbox. Attackers then used these stolen credentials to try to log in to sites across the internet, including Dropbox”.
**Source: Dropbox. [https://blog.dropbox.com/2014/10/dropbox-wasnt-hacked/]

*JPMC, 2014: “[The breached data] contained some of the combinations of passwords and email addresses used by race participants who had registered on the Corporate Challenge website, an online platform for a series of annual charitable races that JPMorgan sponsors in major cities and that is run by an outside vendor. The races are open to bank employees and employees of other corporations”.
**Source: NY Times. [http://dealbook.nytimes.com/2014/10/31/discovery-of-jpmorgan-cyberattack-aided-by-company-that-runs-race-website-for-bank/]

This connected chain of events from Sony to Yahoo to Dropbox excludes JPMC. The JPMC breach came from a separate and unrelated source. We know that the JPMC breach was caused by attackers targeting an unrelated third-party athletic race/run site for credentials to use against JPMC.

== Related Threat Agents ==

== Related Attacks ==

== Related Vulnerabilities ==

== Related Controls ==

== References ==

2014-04-10T19:02:51Z

Neal Mueller:

[[File:Heartbleed.png]]

= Introduction =

Heartbleed is a catastrophic bug in OpenSSL, announced in April 2014.

= About the Name =

Like most major vulnerabilities, this major vulnerability is well branded. It gets it's name from the heart beat function between client and server. According to Dan Kaminsky [https://itunes.apple.com/us/podcast/apm-marketplace-tech-report/id73330855], "When you are communicating with another computer, sometimes you have a pulse message that says 'yes I'm still here'. This is a heart beat. In this particular case there is the possibility to leak information from the heartbeat, so you don't just know that someone is on the other side, you know something about them. In this case, you know too much. There's a bleeding of information from the heartbeat."

= Timing =

'''What's known:'''
The vulnerability became public on April 7, 2014 after being independently discovered by Google Security and Codenomicon.
The vulnerability was widely reported on April 9, 2014.
The vulnerable versions have been widely used for two years.

'''Has this been abused in the wild? '''
We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts. According to Bruce Schneier, [https://www.schneier.com/blog/archives/2014/04/heartbleed.html] "The real question is whether or not someone deliberately inserted this bug into OpenSSL, and has had two years of unfettered access to everything. My guess is accident, but I have no proof." According to EFF, intelligence agencies may have been using heartbleed in November 2013. Source: [https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013]

= Severity =

According to Bruce Schneier [https://www.schneier.com/blog/archives/2014/04/heartbleed.html], "Catastrophic is the right word. On the scale of 1 to 10, this is an 11." Counterpoint also from Bruce Schneier, "If nothing really bad happens -- if this turns out to be something like the Y2K bug -- then we are going to face criticisms of crying wolf."

According to Codenomicon [http://heartbleed.com/], "There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed."

= Impact of the Vulnerability =

This vulnerability allows an attacker to extract memory contents from the webserver through the vulnerability in the heartbeat. As a result an attacker may be able to access sensitive information such as the private keys used for SSL/TLS.

'''Active Attack''' - Equipped with the private key, an attacker can silently monitor and decrypt communications between the user and the web server. As a result, an attacker could view private data such as passwords, credit card data, medical records and any other sensitive data the user exchanges with the website. In addition, the attacker could impersonate the target website to deliver fake, inaccurate or malicious data to the user.

'''Offline Attack''' - Some well funded attackers gather large amounts of encrypted data and store this data in the event they can later decrypt the information. Using the Heartbleed vulnerability the attackers could decrypt this information if it was obtained when passed between a user and a vulnerable website. This means that sensitive data exchanged up to two years ago could also now be at risk for exposure to attackers. Note: sites implementing Perfect Forward Secrecy are protected against this particular attack.

'''Scope''' - 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1. Apache, which uses OpenSSL for HTTPS, is used by 66% of all websites according to netcraft.com. A study of the TLS heartbeat extension by Netcraft also identified that 17.5% of SSL sites may be vulnerable to the Heartbleed bug.

= Defending against Vulnerability =

'''What should website owners do?'''

Verify if you are using a vulnerable version of OpenSSL.

Upgrade OpenSSL as soon as possible. OpenSSL 1.0.1g was released on April 7, 2014 (https://www.openssl.org/source/).

Reissue your security certificates for SSL/TLS. The vulnerability has been present for two years and there is no way to verify if your private key has been compromised as a result of this vulnerability. In addition, a compromised key would be used to silently monitor communications from your users and the attack would be undetectable. It is prudent to assume a breach and proactively reissue security certificates.

Implement Perfect Forward Secrecy. This additional layer of security protects encrypted data from several potential attacks by using a per session random keys.

'''What should users do?'''

Unfortunately there’s not much a user can do. If you have an account at one of the many large websites that may have been affected, you can proactively change your password just to be safe.

According to Errata Security [http://blog.erratasec.com/2014/04/yes-you-might-have-to-change-your.html#.U0blvq1dWv0], "The only passwords you need to change would be ones that you entered in the last couple of days. Personally, I haven't entered any passwords over the last couple days, so I don't need to change any passwords."

= Links for More Information =

Heartbleed page from Codenomicon [http://heartbleed.com/]

Test a website's vulnerability here [http://filippo.io/Heartbleed/]

Blog post from Michael Coates [[http://blog.shapesecurity.com/heartbleed-bug-places-encrypted-user-data-and-webservers-at-risk]]

XKCD cartoon [https://xkcd.com/1353]

[[Category:Vulnerability]]

2014-04-10T18:41:13Z

Neal Mueller:

Heartbleed Bug

2014-04-10T18:29:38Z

Neal Mueller:

= Introduction =

Heartbleed is a catastrophic bug in OpenSSL, announced in April 2014.

= About the Name =

Like most major vulnerabilities, this major vulnerability is well branded. It gets it's name from the heart beat function between client and server. According to Dan Kaminsky, "When you are communicating with another computer, sometimes you have a pulse message that says 'yes I'm still here'. This is a heart beat. In this particular case there is the possibility to leak information from the heartbeat, so you don't just know that someone is on the other side, you know something about them. In this case, you know too much. There's a bleeding of information from the heartbeat."

= Timing =

'''What's known:'''
The vulnerability became public on April 7, 2014 after being independently discovered by Google Security and Codenomicon.
The vulnerability was widely reported on April 9, 2014.
The vulnerable versions have been widely used for two years.

'''Has this been abused in the wild? '''
We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts. According to Bruce Schneier, "The real question is whether or not someone deliberately inserted this bug into OpenSSL, and has had two years of unfettered access to everything. My guess is accident, but I have no proof." According to EFF, intelligence agencies may have been using heartbleed in November 2013. Source: [https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013]

= Severity =

According to Bruce Schneier, "Catastrophic is the right word. On the scale of 1 to 10, this is an 11." Counterpoint also from Bruce Schneier, "If nothing really bad happens -- if this turns out to be something like the Y2K bug -- then we are going to face criticisms of crying wolf."

According to Codenomicon, "There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed."

= Impact of the Vulnerability =

This vulnerability allows an attacker to extract memory contents from the webserver through the vulnerability in the heartbeat. As a result an attacker may be able to access sensitive information such as the private keys used for SSL/TLS.

'''Active Attack''' - Equipped with the private key, an attacker can silently monitor and decrypt communications between the user and the web server. As a result, an attacker could view private data such as passwords, credit card data, medical records and any other sensitive data the user exchanges with the website. In addition, the attacker could impersonate the target website to deliver fake, inaccurate or malicious data to the user.

'''Offline Attack''' - Some well funded attackers gather large amounts of encrypted data and store this data in the event they can later decrypt the information. Using the Heartbleed vulnerability the attackers could decrypt this information if it was obtained when passed between a user and a vulnerable website. This means that sensitive data exchanged up to two years ago could also now be at risk for exposure to attackers. Note: sites implementing Perfect Forward Secrecy are protected against this particular attack.

'''Scope''' - 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1. Apache, which uses OpenSSL for HTTPS, is used by 66% of all websites according to netcraft.com. A study of the TLS heartbeat extension by Netcraft also identified that 17.5% of SSL sites may be vulnerable to the Heartbleed bug.

= Defending against Vulnerability =

'''What should website owners do?'''

Verify if you are using a vulnerable version of OpenSSL.

Upgrade OpenSSL as soon as possible. OpenSSL 1.0.1g was released on April 7, 2014 (https://www.openssl.org/source/).

Reissue your security certificates for SSL/TLS. The vulnerability has been present for two years and there is no way to verify if your private key has been compromised as a result of this vulnerability. In addition, a compromised key would be used to silently monitor communications from your users and the attack would be undetectable. It is prudent to assume a breach and proactively reissue security certificates.

Implement Perfect Forward Secrecy. This additional layer of security protects encrypted data from several potential attacks by using a per session random keys.

'''What should users do?'''

Unfortunately there’s not much a user can do. If you have an account at one of the many large websites that may have been affected, you can proactively change your password just to be safe.

According to Errata Security, "The only passwords you need to change would be ones that you entered in the last couple of days. Personally, I haven't entered any passwords over the last couple days, so I don't need to change any passwords."

= Links for More Information =

Heartbleed page from Codenomicon [http://heartbleed.com/]

Test a website's vulnerability here [http://filippo.io/Heartbleed/]

Blog post from Michael Coates [[http://blog.shapesecurity.com/heartbleed-bug-places-encrypted-user-data-and-webservers-at-risk]]

XKCD cartoon [https://xkcd.com/1353]

Heartbleed Bug

2014-04-10T18:29:07Z

Neal Mueller:

= Introduction =

Heartbleed is a catastrophic bug in OpenSSL, announced in April 2014.

= About the Name =

Like most major vulnerabilities, this major vulnerability is well branded. It gets it's name from the heart beat function between client and server. According to Dan Kaminsky, "When you are communicating with another computer, sometimes you have a pulse message that says 'yes I'm still here'. This is a heart beat. In this particular case there is the possibility to leak information from the heartbeat, so you don't just know that someone is on the other side, you know something about them. In this case, you know too much. There's a bleeding of information from the heartbeat."

= Timing =

'''What's known:'''
The vulnerability became public on April 7, 2014 after being independently discovered by Google Security and Codenomicon.
The vulnerability was widely reported on April 9, 2014.
The vulnerable versions have been widely used for two years.

'''Has this been abused in the wild? '''
We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts. According to Bruce Schneier, "The real question is whether or not someone deliberately inserted this bug into OpenSSL, and has had two years of unfettered access to everything. My guess is accident, but I have no proof." According to EFF, intelligence agencies may have been using heartbleed in November 2013. Source: [https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013]

= Severity =

According to Bruce Schneier, "Catastrophic is the right word. On the scale of 1 to 10, this is an 11." Counterpoint also from Bruce Schneier, "If nothing really bad happens -- if this turns out to be something like the Y2K bug -- then we are going to face criticisms of crying wolf."

According to Codenomicon, "There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed."

= Impact of the Vulnerability =

This vulnerability allows an attacker to extract memory contents from the webserver through the vulnerability in the heartbeat. As a result an attacker may be able to access sensitive information such as the private keys used for SSL/TLS.

'''Active Attack''' - Equipped with the private key, an attacker can silently monitor and decrypt communications between the user and the web server. As a result, an attacker could view private data such as passwords, credit card data, medical records and any other sensitive data the user exchanges with the website. In addition, the attacker could impersonate the target website to deliver fake, inaccurate or malicious data to the user.

'''Offline Attack''' - Some well funded attackers gather large amounts of encrypted data and store this data in the event they can later decrypt the information. Using the Heartbleed vulnerability the attackers could decrypt this information if it was obtained when passed between a user and a vulnerable website. This means that sensitive data exchanged up to two years ago could also now be at risk for exposure to attackers. Note: sites implementing Perfect Forward Secrecy are protected against this particular attack.

'''Scope'''

1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1.

Apache, which uses OpenSSL for HTTPS, is used by 66% of all websites according to netcraft.com. A study of the TLS heartbeat extension by Netcraft also identified that 17.5% of SSL sites may be vulnerable to the Heartbleed bug.

= Defending against Vulnerability =

'''What should website owners do?'''

Verify if you are using a vulnerable version of OpenSSL.

Upgrade OpenSSL as soon as possible. OpenSSL 1.0.1g was released on April 7, 2014 (https://www.openssl.org/source/).

Reissue your security certificates for SSL/TLS. The vulnerability has been present for two years and there is no way to verify if your private key has been compromised as a result of this vulnerability. In addition, a compromised key would be used to silently monitor communications from your users and the attack would be undetectable. It is prudent to assume a breach and proactively reissue security certificates.

Implement Perfect Forward Secrecy. This additional layer of security protects encrypted data from several potential attacks by using a per session random keys.

'''What should users do?'''

Unfortunately there’s not much a user can do. If you have an account at one of the many large websites that may have been affected, you can proactively change your password just to be safe.

According to Errata Security, "The only passwords you need to change would be ones that you entered in the last couple of days. Personally, I haven't entered any passwords over the last couple days, so I don't need to change any passwords."

= Links for More Information =

Heartbleed page from Codenomicon [http://heartbleed.com/]

Test a website's vulnerability here [http://filippo.io/Heartbleed/]

Blog post from Michael Coates [[http://blog.shapesecurity.com/heartbleed-bug-places-encrypted-user-data-and-webservers-at-risk]]

XKCD cartoon [https://xkcd.com/1353]

Heartbleed Bug

2014-04-10T18:28:19Z

Neal Mueller: Heartbleed is a catastrophic bug in OpenSSL

[[File:http://heartbleed.com/heartbleed.png]]

= Introduction =

Heartbleed is a catastrophic bug in OpenSSL, announced in April 2014.

= About the Name =

Like most major vulnerabilities, this major vulnerability is well branded. It gets it's name from the heart beat function between client and server. According to Dan Kaminsky, "When you are communicating with another computer, sometimes you have a pulse message that says 'yes I'm still here'. This is a heart beat. In this particular case there is the possibility to leak information from the heartbeat, so you don't just know that someone is on the other side, you know something about them. In this case, you know too much. There's a bleeding of information from the heartbeat."

= Timing =

'''What's known:'''
The vulnerability became public on April 7, 2014 after being independently discovered by Google Security and Codenomicon.
The vulnerability was widely reported on April 9, 2014.
The vulnerable versions have been widely used for two years.

'''Has this been abused in the wild? '''
We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts. According to Bruce Schneier, "The real question is whether or not someone deliberately inserted this bug into OpenSSL, and has had two years of unfettered access to everything. My guess is accident, but I have no proof." According to EFF, intelligence agencies may have been using heartbleed in November 2013. Source: [https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013]

= Severity =

According to Bruce Schneier, "Catastrophic is the right word. On the scale of 1 to 10, this is an 11." Counterpoint also from Bruce Schneier, "If nothing really bad happens -- if this turns out to be something like the Y2K bug -- then we are going to face criticisms of crying wolf."

According to Codenomicon, "There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed."

= Impact of the Vulnerability =

This vulnerability allows an attacker to extract memory contents from the webserver through the vulnerability in the heartbeat. As a result an attacker may be able to access sensitive information such as the private keys used for SSL/TLS.

'''Active Attack''' - Equipped with the private key, an attacker can silently monitor and decrypt communications between the user and the web server. As a result, an attacker could view private data such as passwords, credit card data, medical records and any other sensitive data the user exchanges with the website. In addition, the attacker could impersonate the target website to deliver fake, inaccurate or malicious data to the user.

'''Offline Attack''' - Some well funded attackers gather large amounts of encrypted data and store this data in the event they can later decrypt the information. Using the Heartbleed vulnerability the attackers could decrypt this information if it was obtained when passed between a user and a vulnerable website. This means that sensitive data exchanged up to two years ago could also now be at risk for exposure to attackers. Note: sites implementing Perfect Forward Secrecy are protected against this particular attack.

'''Scope'''

1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1.

Apache, which uses OpenSSL for HTTPS, is used by 66% of all websites according to netcraft.com. A study of the TLS heartbeat extension by Netcraft also identified that 17.5% of SSL sites may be vulnerable to the Heartbleed bug.

= Defending against Vulnerability =

'''What should website owners do?'''

Verify if you are using a vulnerable version of OpenSSL.

Upgrade OpenSSL as soon as possible. OpenSSL 1.0.1g was released on April 7, 2014 (https://www.openssl.org/source/).

Reissue your security certificates for SSL/TLS. The vulnerability has been present for two years and there is no way to verify if your private key has been compromised as a result of this vulnerability. In addition, a compromised key would be used to silently monitor communications from your users and the attack would be undetectable. It is prudent to assume a breach and proactively reissue security certificates.

Implement Perfect Forward Secrecy. This additional layer of security protects encrypted data from several potential attacks by using a per session random keys.

'''What should users do?'''

Unfortunately there’s not much a user can do. If you have an account at one of the many large websites that may have been affected, you can proactively change your password just to be safe.

According to Errata Security, "The only passwords you need to change would be ones that you entered in the last couple of days. Personally, I haven't entered any passwords over the last couple days, so I don't need to change any passwords."

= Links for More Information =

Heartbleed page from Codenomicon [http://heartbleed.com/]

Test a website's vulnerability here [http://filippo.io/Heartbleed/]

Blog post from Michael Coates [[http://blog.shapesecurity.com/heartbleed-bug-places-encrypted-user-data-and-webservers-at-risk]]

XKCD cartoon [https://xkcd.com/1353]