Known Vulnerabilities for Boringssl by Google
Listed below are 1 of the newest known vulnerabilities associated with "Boringssl" by "Google".
These CVEs are retrieved based on exact matches on listed software, hardware, and vendor information (CPE data) as well as a keyword search to ensure the newest vulnerabilities with no officially listed software information are still displayed.
Data on known vulnerable versions is also displayed based on information from known CPEs
|CVE||Shortened Description||Severity||Publish Date||Last Modified|
|CVE-2018-12440||BoringSSL through 2018-06-14 allows a memory-cache side-channel attack on DSA signatures, aka the Return Of the Hidden Number...||4.7 - MEDIUM||2018-06-15||2018-08-06|
Known Affected Configurations (CPE V2.3)
Popular searches for Boringssl
Git at Google BoringSSL 3 1 / is a fork of OpenSSL that is designed to meet Google Although BoringSSL OpenSSL is. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability. BoringSSL arose because Google OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL.OpenSSL Google Application programming interface Git Patch (computing) Fork (software development) Open-source software Application binary interface Upstream (software development) Mkdir .md Android (operating system) Mdadm Google Chrome Android software development Transport Layer Security Computer program Library (computing) Backward compatibility Programming style
oogle/boringssl Mirror of BoringSSL Contribute to google GitHub.OpenSSL GitHub Application programming interface SHA-1 Adobe Contribute Mkdir Google Byte Advanced Encryption Standard Patch (computing) Megabyte Open-source software .md Command-line interface Block cipher mode of operation Repository (version control) Xcode Microsoft Visual Studio Fork (software development) Software repository