Mbed Tls: A security weakness

Mbed Tls is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.8 CVSS · secalert@redhat.com

NVD score 6.8 CVSS 2.0 · nvd@nist.gov

Component: Mbed Tls
Plugin slug: mbed-tls
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Nov 02, 2015
Weakness: CWE-119 — Improper Restriction of Operations within the Bounds of a Memory Buffer

This CVE was published Nov 02, 2015 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Mbed Tls to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

Heap-based buffer overflow in PolarSSL 1.x before 1.2.17 and ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and possibly execute arbitrary code via a long hostname to the server name indication (SNI) extension, which is not properly handled when creating a ClientHello message. NOTE: this identifier has been SPLIT per ADT3 due to different affected version ranges. See CVE-2015-8036 for the session ticket issue that was introduced in 1.3.0.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Update, patch or deactivate.

Technical description

Primary and upstream sources