From ce3a4bae56224581ae7e2423af76e97147eb8ef0 Mon Sep 17 00:00:00 2001 From: J08nY Date: Wed, 25 Dec 2019 22:03:11 +0100 Subject: Update Travis, add info about new supported libs. --- docs/LIBS.md | 22 ++++++++++++++++------ docs/VULNS.md | 8 ++++---- 2 files changed, 20 insertions(+), 10 deletions(-) (limited to 'docs') diff --git a/docs/LIBS.md b/docs/LIBS.md index 9c90abf..b9d1db9 100644 --- a/docs/LIBS.md +++ b/docs/LIBS.md @@ -119,17 +119,27 @@ ninja - Uses 5-bit window NAF. - Uses Jacobian coordinates. - - + - [Nettle](http://www.lysator.liu.se/~nisse/nettle/) + - C + - No support for explicit parameters, only SECG named curves. + - Uses Jacobian coordinates. + - + - + - + - Uses double-and-add always or windowing algorithm. + - Uses Pippenger scalar mult for Twisted Edwards curves. + - [LibreSSL](https://www.libressl.org/) + - C # Libraries with ECC support Popular libraries with at least some ECC support, that ECTester does not yet support: - [NSS](https://hg.mozilla.org/projects/nss) - - [LibreSSL](https://www.libressl.org/) - - [Nettle](http://www.lysator.liu.se/~nisse/nettle/) - - [BearSSL](https://bearssl.org/) - - [cryptlib](https://www.cryptlib.com/) + - [BearSSL](https://bearssl.org/)* + - [cryptlib](https://www.cryptlib.com/)* - [OpenSSL (FIPS mode)](https://www.openssl.org/docs/fipsnotes.html) - [Microsoft .NET crypto](https://docs.microsoft.com/en-us/dotnet/standard/security/cryptography-model) - - [Linux kernel](https://kernel.org), test via [libkcapi](http://chronox.de/libkcapi.html) \ No newline at end of file + - [Linux kernel](https://kernel.org), test via [libkcapi](http://chronox.de/libkcapi.html) + +* Signifies libraries for which adding support would be very much appreciated. \ No newline at end of file diff --git a/docs/VULNS.md b/docs/VULNS.md index 36e66d1..d7117b5 100644 --- a/docs/VULNS.md +++ b/docs/VULNS.md @@ -2,9 +2,9 @@ ## Cards -| CVE | Card | CVSS v3 | Description | Discoverer | -|:-------------------------------------------------------------------------------:|:------------------------:|:-------:| ----------- |:----------:| -| [CVE-2019-15809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15809) | Athena IDProtect | | Smart cards from the Athena SCS manufacturer, based on the Atmel Toolbox 00.03.11.05 and the AT90SC chip, contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because the Atmel Toolbox 00.03.11.05 contains two versions of ECDSA signature functions, described as fast and secure, but the affected cards chose to use the fast version, which leaks the bit length of the random nonce via timing. This affects:
  • Athena IDProtect 010b.0352.0005
  • Athena IDProtect 010e.1245.0002
  • Athena IDProtect 0106.0130.0401
  • Athena IDProtect 010e.1245.0002
  • Valid S/A IDflex V 010b.0352.0005
  • SafeNet eToken 4300 010e.1245.0002
  • TecSec Armored Card 010e.0264.0001
  • TecSec Armored Card 0108.0264.0001
| [Jan Jancar](https://github.com/J08nY) | +| CVE | Card | CVSS v3 | Description | Discoverer | +|:-------------------------------------------------------------------------------:|:------------------------:|:---------:| ----------- |:----------:| +| [CVE-2019-15809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15809) | Athena IDProtect | 4.7 MEDIUM| Smart cards from the Athena SCS manufacturer, based on the Atmel Toolbox 00.03.11.05 and the AT90SC chip, contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because the Atmel Toolbox 00.03.11.05 contains two versions of ECDSA signature functions, described as fast and secure, but the affected cards chose to use the fast version, which leaks the bit length of the random nonce via timing. This affects:
  • Athena IDProtect 010b.0352.0005
  • Athena IDProtect 010e.1245.0002
  • Athena IDProtect 0106.0130.0401
  • Athena IDProtect 010e.1245.0002
  • Valid S/A IDflex V 010b.0352.0005
  • SafeNet eToken 4300 010e.1245.0002
  • TecSec Armored Card 010e.0264.0001
  • TecSec Armored Card 0108.0264.0001
| [Jan Jancar](https://github.com/J08nY) | ## Libraries @@ -14,5 +14,5 @@ | [CVE-2019-13627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13627) | libgcrypt | 5.9 MEDIUM| Libgcrypt 1.3.0 through 1.8.4 (ECDSA) and 1.6.0 through 1.8.4 (EdDSA) contains a timing side channel in ECDSA/EdDSA signature generation. This allows a local or a remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because mpi/ec.c scalar multiplication leaks the bit length of the scalar.| [Jan Jancar](https://github.com/J08nY)| | [CVE-2019-13628](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13628) | wolfCrypt, wolfSSL | 5.9 MEDIUM| wolfSSL and wolfCrypt 4.0.0 and earlier (when configured without --enable-fpecc, --enable-sp, or --enable-sp-math) contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to precisely measure the duration of signature operations, to infer information about the nonces used and potentially mount a lattice attack to recover the private key used. The issue occurs because ecc.c scalar multiplication might leak the bit length.| [Jan Jancar](https://github.com/J08nY)| | [CVE-2019-13629](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13629) | MatrixSSL | 5.9 MEDIUM| MatrixSSL 4.2.1 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or a remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because crypto/pubkey/ecc_math.c scalar multiplication leaks the bit length of the scalar.| [Jan Jancar](https://github.com/J08nY) | -| [CVE-2019-14317](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14317) | wolfCrypt, wolfSSL | | wolfSSL and wolfCrypt 4.1.0 and earlier (formerly known as CyaSSL) generate biased DSA nonces. This allows a remote attacker to compute the long term private key from several hundred DSA signatures via a lattice attack. The issue occurs because dsa.c fixes two bits of the generated nonces.| [Jan Jancar](https://github.com/J08nY)| +| [CVE-2019-14317](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14317) | wolfCrypt, wolfSSL | 5.3 MEDIUM| wolfSSL and wolfCrypt 4.1.0 and earlier (formerly known as CyaSSL) generate biased DSA nonces. This allows a remote attacker to compute the long term private key from several hundred DSA signatures via a lattice attack. The issue occurs because dsa.c fixes two bits of the generated nonces.| [Jan Jancar](https://github.com/J08nY)| | [CVE-2019-14318](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14318) | Crypto++ | 5.9 MEDIUM| Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.| [Jan Jancar](https://github.com/J08nY)| -- cgit v1.2.3-70-g09d2