Recently a bug was found in the popular cryptographic software library Openssl
This information was gotten from the official documentation on Heartbleed.com
The Heartbleed Bug
The Heartbleed Bug is a serious vulnerability in the
popular OpenSSL cryptographic software library. This weakness allows
stealing the information protected, under normal conditions, by the
SSL/TLS encryption used to secure the Internet. SSL/TLS provides
communication security and privacy over the Internet for applications
such as web, email, instant messaging (IM) and some virtual private
networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
What leaks in practice?
We have tested some of our own services from attacker's perspective. We attacked ourselves from outside, without leaving a trace. Without using any privileged information or credentials we were able steal from ourselves the secret keys used for our X.509 certificates, user names and passwords, instant messages, emails and business critical documents and communication.How to stop the leak?
As long as the vulnerable version of OpenSSL is in use it can be abused. Fixed OpenSSL has been released and now it has to be deployed. Operating system vendors and distribution, appliance vendors, independent software vendors have to adopt the fix and notify their users. Service providers and users have to install the fix as it becomes available for the operating systems, networked appliances and software they use.Q&A
What is the CVE-2014-0160?
CVE-2014-0160 is the official reference to this bug. CVE
(Common Vulnerabilities and Exposures) is the Standard for Information
Security Vulnerability Names maintained by MITRE.
Due to co-incident discovery a duplicate CVE, CVE-2014-0346, which was
assigned to us, should not be used, since others independently went
public with the CVE-2014-0160 identifier.
To test if your server is affected by the bug Run Test here, or visit the repo, to be aware
To test if your server is affected by the bug Run Test here, or visit the repo, to be aware
Why it is called the Heartbleed Bug?
Bug is in the OpenSSL's implementation of the TLS/DTLS
(transport layer security protocols) heartbeat extension (RFC6520). When
it is exploited it leads to the leak of memory contents from the server
to the client and from the client to the server.
What makes the Heartbleed Bug unique?
Bugs in single software or library come and go and are
fixed by new versions. However this bug has left large amount of private
keys and other secrets exposed to the Internet. Considering the long
exposure, ease of exploitation and attacks leaving no trace this
exposure should be taken seriously.
Is this a design flaw in SSL/TLS protocol specification?
No. This is implementation problem, i.e. programming
mistake in popular OpenSSL library that provides cryptographic services
such as SSL/TLS to the applications and services.
What is being leaked?
Encryption is used to protect secrets that may harm your
privacy or security if they leak. In order to coordinate recovery from
this bug we have classified the compromised secrets to four categories:
1) primary key material, 2) secondary key material and 3) protected
content and 4) collateral.
What is leaked primary key material and how to recover?
These are the crown jewels, the encryption keys themselves.
Leaked secret keys allows the attacker to decrypt any past and future
traffic to the protected services and to impersonate the service at
will. Any protection given by the encryption and the signatures in the
X.509 certificates can be bypassed. Recovery from this leak requires
patching the vulnerability, revocation of the compromised keys and
reissuing and redistributing new keys. Even doing all this will still
leave any traffic intercepted by the attacker in the past still
vulnerable to decryption. All this has to be done by the owners of the
services.
What is leaked secondary key material and how to recover?
These are for example the user credentials (user names and
passwords) used in the vulnerable services. Recovery from this leaks
requires owners of the service first to restore trust to the service
according to steps described above. After this users can start changing
their passwords and possible encryption keys according to the
instructions from the owners of the services that have been compromised.
All session keys and session cookies should be invalided and considered
compromised.
What is leaked protected content and how to recover?
This is the actual content handled by the vulnerable
services. It may be personal or financial details, private communication
such as emails or instant messages, documents or anything seen worth
protecting by encryption. Only owners of the services will be able to
estimate the likelihood what has been leaked and they should notify
their users accordingly. Most important thing is to restore trust to the
primary and secondary key material as described above. Only this
enables safe use of the compromised services in the future.
What is leaked collateral and how to recover?
Leaked collateral are other details that have been exposed
to the attacker in the leaked memory content. These may contain
technical details such as memory addresses and security measures such as
canaries used to protect against overflow attacks. These have only
contemporary value and will lose their value to the attacker when
OpenSSL has been upgraded to a fixed version.
Recovery sounds laborious, is there a short cut?
After seeing what we saw by "attacking" ourselves, with
ease, we decided to take this very seriously. We have gone laboriously
through patching our own critical services and are in progress of
dealing with possible compromise of our primary and secondary key
material. All this just in case we were not first ones to discover this
and this could have been exploited in the wild already.
How revocation and reissuing of certificates works in practice?
If you are a service provider you have signed your
certificates with a Certificate Authority (CA). You need to check your
CA how compromised keys can be revoked and new certificate reissued for
the new keys. Some CAs do this for free, some may take a fee.
visit heartbleed for more information