Heartbleed affects which TLS library's implementation?

Heartbleed affects which TLS library's implementation?

• A. OpenSSL
• B. BoringSSL
• C. LibreSSL
• D. WolfSSL

Answer: (A)

Heartbleed is a vulnerability in the TLS heartbeat feature that showed up in the OpenSSL implementation. The bug occurred because the code didn’t properly bound-check the heartbeat payload, so an attacker could cause a server to echo back more data than requested and read memory contents. This flaw existed in OpenSSL’s heartbeat handling, not in the other libraries listed (which are separate projects or forks and did not contain the vulnerable path in the same way). So the library affected by the original Heartbleed bug is OpenSSL.

Heartbleed is a vulnerability in the TLS heartbeat feature that showed up in the OpenSSL implementation. The bug occurred because the code didn’t properly bound-check the heartbeat payload, so an attacker could cause a server to echo back more data than requested and read memory contents. This flaw existed in OpenSSL’s heartbeat handling, not in the other libraries listed (which are separate projects or forks and did not contain the vulnerable path in the same way). So the library affected by the original Heartbleed bug is OpenSSL.