CVE-2016-6878: Input Validation
First published: Mon Apr 10 2017(Updated: )
The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to have unspecified impact via vectors related to undefined behavior, as demonstrated on 32-bit ARM systems compiled by Clang.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Botan | <=1.11.30 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-6878?
CVE-2016-6878 has a moderate severity due to potential exploits that could cause undefined behavior on affected systems.
How do I fix CVE-2016-6878?
To fix CVE-2016-6878, upgrade to Botan version 1.11.31 or later.
Which versions of Botan are affected by CVE-2016-6878?
Botan versions up to and including 1.11.30 are affected by CVE-2016-6878.
What platforms are primarily impacted by CVE-2016-6878?
CVE-2016-6878 primarily impacts 32-bit ARM systems that lack a native 128-bit integer type.
Can CVE-2016-6878 lead to arbitrary code execution?
While CVE-2016-6878 does not explicitly state arbitrary code execution, its undefined behavior could potentially lead to various impacts depending on the exploitation vector.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/botan project
- canonical/botan
- version/botan/1.11.30