As many of you know, a serious vulnerability in the OpenSSL cryptographic software library was recently discovered: CVE-2014-0160. This vulnerability is commonly called the “Heartbleed Bug” and is described at http://heartbleed.com.
The Heartbleed vulnerability can be exploited by an attacker to gain access to the cryptographic keys used to secure communication between clients and servers using SSL, which includes most communication with web servers using HTTPS. Furthermore, this vulnerability can be used to access the system memory of running servers. As a result, an attacker can potentially listen to client-server traffic, steal passwords, and even hijack an HTTP session.
What actions are we taking?
On Monday we patched all services most vulnerable to attack and since then we have been carefully reviewing the less vulnerable components in our system and either patching or disabling them as appropriate.
We have patched all front-facing web services that talk over HTTPS to include the latest protected version of OpenSSL.
We have regenerated all SSL certificates used by MongoLab web servers, and we have revoked our old certificates.
We have reset all browser sessions active prior to the vulnerability.
We have reviewed the vulnerability of all database hosts and temporarily disabled any features that use the OpenSSL library. These services will remain disabled until they have been patched. Please note that your MongoDB servers are not using the affected library and that your database instances are not vulnerable to direct attack.
What actions should you be taking?
We have no evidence that any customer assets have been compromised. However, there are precautionary steps you should now take to ensure that your MongoLab account and MongoLab databases are as secure as possible:
(1) You should change all mongolab.com account user passwords and audit your list of MongoLab account users to ensure that all users in your MongoLab account are legitimate.
You can change your password on the User settings page which you can link to from the upper-right corner of the screen underneath the “Logout” button.
(2) You should re-generate all user API keys. We suggest you do this even if you have never used your MongoLab API key.
These API keys are per MongoLab user and can be regenerated on the same screen that you use to reset your password in step (1) above.
(3) You should reset all database credentials for all of the database deployments you have with MongoLab and audit the list of users in each database to ensure that all users are legitimate.
To manage database credentials, navigate to your database and click on the “Users” tab.
(4) If you are not using it already, you should enable 2-factor authentication (2FA) for your MongoLab account user.
While we have closed all obvious attack vectors we will continue to respond to this threat by carefully reviewing all of our infrastructure and taking additional actions we deem necessary or prudent.
For updates please see our status page, which we will be keeping up-to-date.
Of course, if you have any questions or concerns please email us at firstname.lastname@example.org.