Customer threat assessment 04MAY2016(openssl vulns)

Security annoucements of interest to the AtomiCorp community, such as vulnerabilities in third party applications.
User avatar
mikeshinn
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 4149
Joined: Thu Feb 07, 2008 7:49 pm
Location: Chantilly, VA

Customer threat assessment 04MAY2016(openssl vulns)

Unread post by mikeshinn »

This report is a daily analysis of all published vulnerabilities in any product, weaknesses in technologies, exploits Internet wide, current internet threats associated with platforms and products our customer use, and if any action is required to protect their assets from these these vulnerabilities, weaknesses and exploits depending on the Atomicorp product they are using.

Please see this forum post for an explanation of the categories used in this report.

CVEs are sometimes created after a vulnerability is published (sometimes far after it has been made public). When CVEs are referenced, it is because a CVE was created today, not because an issue was resolved today, and it is included here for reference.

ASL users

Summary: OpenSSL update recommended.

Already protected against/Known Method/No update required

CVE-2016-2108, High severity: It a ASN.1 encoding issue (CVE-2016-2108) that could cause an out of bounds write leading to memory corruption. This could be exploitable in some configurations. (ASL systems are not exploitable)

CVE-2016-2105,Low severity: This is a heap overflow resulting in heap corruption. The vulnerable function is internal to OpenSSL and is not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2106, Low severity: This appears to be the same function as CVE-2016-2105 and because it is only used internally to OpenSSL it is not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2109, Low severity: Is a resource exhaustion and/or memory exhaustion issue in the ASN.1 read. This is internal to OpenSSL and not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2176, Low severity: An ASN.1 overread could result in access to arbitrary stack information being returned. The release is not clear on exploitability. (ASL systems are not exploitable)

Not already protected against/New Method/Update Available

None.

Not already protected against/Doesnt protect against/Solution

CVE-2016-2107, High severity: A padding attack could be used to permit an attacker who is in a position to Man-in-the-Middle the session to decrypt traffic. (Patches are not available yet from Linux distributors for effected systems)

Potential Vulnerability/Solution

None.

Rules only users

Summary: OpenSSL vulnerabilities, potentially remotelty exploitable.

Already protected against/Known Method/No update required

None.

Not already protected against/New Method/Update Available

None.

Not already protected against/Doesnt protect against/Solution


Modsecurity can not protect against system level vulnerabilities such as these:

CVE-2016-2108, High severity: It a ASN.1 encoding issue (CVE-2016-2108) that could cause an out of bounds write leading to memory corruption. This could be exploitable in some configurations. (ASL systems are not exploitable)

CVE-2016-2105,Low severity: This is a heap overflow resulting in heap corruption. The vulnerable function is internal to OpenSSL and is not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2106, Low severity: This appears to be the same function as CVE-2016-2105 and because it is only used internally to OpenSSL it is not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2109, Low severity: Is a resource exhaustion and/or memory exhaustion issue in the ASN.1 read. This is internal to OpenSSL and not believed to be exploitable. (ASL systems are not exploitable)

CVE-2016-2176, Low severity: An ASN.1 overread could result in access to arbitrary stack information being returned. The release is not clear on exploitability. (ASL systems are not exploitable)


Potential Vulnerability/Solution

None.
Post Reply