CVE-2017-2784 - Freeing of memory allocated on stack when validating a public key with a secp224k1 curve
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mbedtls (Debian) |
Fix Released
|
Unknown
|
|||
mbedtls (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
polarssl (Debian) |
Fix Released
|
Unknown
|
|||
polarssl (Ubuntu) |
Incomplete
|
Medium
|
Unassigned | ||
Xenial |
Confirmed
|
Undecided
|
Unassigned | ||
Yakkety |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The following security bug was published for mbedtls:
Freeing of memory allocated on stack when validating a public key with a secp224k1 curve
[Vulnerability]
If a malicious peer supplies a certificate with a specially crafted secp224k1 public key, then an attacker can cause the server or client to attempt to free block of memory held on stack.
[Impact]
Depending on the platform, this could result in a Denial of Service (client crash) or potentially could be exploited to allow remote code execution with the same privileges as the host application.
[Resolution]
Affected users should upgrade to mbed TLS 1.3.19, mbed TLS 2.1.7 or mbed TLS 2.4.2.
https:/
CVE References
information type: | Private Security → Public Security |
Changed in polarssl (Debian): | |
status: | Unknown → Confirmed |
Changed in mbedtls (Debian): | |
status: | Incomplete → Fix Released |
summary: |
- CVE-2017-2748 - Freeing of memory allocated on stack when validating a + CVE-2017-2784 - Freeing of memory allocated on stack when validating a public key with a secp224k1 curve |
Changed in polarssl (Debian): | |
status: | Incomplete → Confirmed |
Changed in polarssl (Ubuntu): | |
importance: | Undecided → Medium |
Changed in mbedtls (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: patch trusty xenial yakkety |
Changed in polarssl (Debian): | |
status: | Confirmed → Fix Committed |
Changed in polarssl (Debian): | |
status: | Fix Committed → Fix Released |
I think that only polarssl 1.3.* is affected because polarssl <= 1.2 does not support elliptic curve crypto.