HexBrain

Hiro · Report #910732

blockstack.org - is vulnerable to (CVE-2016-2183, CVE-2016-6329)

Informativestatus
9upvotes
31 Oct 2025disclosed

How it was found

Descriptions Cryptographic protocols like TLS, SSH, IPsec, and OpenVPN commonly use block cipher algorithms, such as AES, Triple-DES, and Blowfish, to encrypt data between clients and servers. To use such algorithms, the data is broken into fixed-length chunks, called blocks, and each block is encrypted separately according to a mode of operation. Older block ciphers, such as Triple-DES and Blowfish use a block size of 64 bits, whereas AES uses a block size of 128 bits. A attacker can can decrypt victim data using Sweet32 birthday attck vulnerability over wifi or (local network) Hackerone Refferals #232463 #375097 #216271 #210331

Steps To Reproduce:

  • open nmap and type: nmap --script ssl-enum-ciphers blockstack.org
  • and wait until it finishes the scan
  • here are the results 64-bit block cipher 3DES vulnerable to SWEET32 attack Key exchange (secp192r1) of lower strength than certificate key

note: this vulnerability and exploitation has been demo'ed at defcon ref site: https://sweet32.info/

Response

443/tcp open  https
| ssl-enum-ciphers:
|   TLSv1.0:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.1:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A

How to fix this vulnerability It's recommended to disable SSLv3 and replace it with TLSv1.0 as soon as compatibility with legacy clients is no longer required. (The only browser that does not support TLSv1.0 is Internet Explorer 6).

To disable SSLv2 and SSLv3: For Nginx: ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

Proof On Concept

  • F886917

Impact

(CVE-2016-2183, CVE-2016-6329)

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original