Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2021-33560 PoC — Libgcrypt 安全漏洞

Source
Associated Vulnerability
Title:Libgcrypt 安全漏洞 (CVE-2021-33560)
Description:Libgcrypt是GNU计划开发(Gnu计划开发)的一个基于GnuPG代码的通用加密库。该库实现了各种加密算法,包括对称密码、哈希算法、公开密钥算法等。 Libgcrypt 在1.8.8和1.9之前存在安全漏洞,该漏洞源于缺乏指数盲法来解决针对mpi powm的侧信道攻击,而且窗口大小选择不当。
Description
Tool to check whether a PGP client is affected by CVE-2021-33560
Readme
# PGP client checker – CVE-2021-33560

This is a tool to check whether your OpenPGP client is affected by
[CVE-2021-33560](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560).

This vulnerability exposes to plaintext recovery the messages you
encrypt to some ElGamal subkeys.  The technical details of the
vulnerability are described in [this blog
post](https://ibm.github.io/system-security-research-updates/2021/07/20/insecurity-elgamal-pt1)
and [this research article](https://eprint.iacr.org/2021/923).

This tool tests whether your OpenPGP client is affected **when acting
as a sender**.  It **does not tell** whether your ElGamal subkeys
**are affected when acting as the recipient**, this is unfortunately a
computationally heavy check that can only be performed by an expert.
If you use ElGamal subkeys and are concerned about their security,
read [our
FAQ](https://ibm.github.io/system-security-research-updates/2021/07/20/insecurity-elgamal-pt1#faq).

## Requirements

You need Python version 3.8 or higher.

## How to use

This tool works by encrypting a message to a specially crafted ElGamal
subkey, then analyzing the produced ciphertext to look for the
vulnerability.

The way you import the public key and encrypt to it depends on your
OpenPGP client.  In the example below, we use GPG (whose libgcrypt is
affected until versions 1.8.8 and 1.9.3), but you will have to adapt
the steps to your own client.

1. Clone this repo and enter it
   
   ```
   git clone https://github.com/IBM/PGP-client-checker-CVE-2021-33560.git
   cd PGP-client-checker-CVE-2021-33560
   ```

2. Import the public key (this step depends on your client)
   
   ```
   gpg --import key.asc
   ```
   
3. Encrypt a message (e.g., "Hi") to the imported key (this step
   depends on your client)
   
   ```
   echo "Hi" | gpg -e --always-trust --armor -r joe@foo.bar --output ciphertext.asc
   ```

4. Run the tool on the obtained ciphertext
   
   ```
   ./sec-check.py ciphertext.asc
   ```
   
   and inspect the output. If your client is affected, you may have a
   message similar to this:
   
   ```
   Inspecting ./ciphertext.asc
   Ephemeral secret bit length: 342
   
   **Your client is affected by CVE-2021-33560!**
   
   Your client seems to be based on an old version of libgcrypt.  If a
   security patch for your client is available, install it!
   ```

## Learn more

To learn more about the vulnerability, read [our technical blog
post](https://ibm.github.io/system-security-research-updates/2021/07/20/insecurity-elgamal-pt1).
File Snapshot

[4.0K] /data/pocs/eb603b2c50b3ac5b11875c5b0bc5e8afce634363 ├── [1.9K] key.asc ├── [ 11K] LICENSE ├── [2.5K] README.md └── [5.1K] sec-check.py 0 directories, 4 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. If the original source is unavailable, please email f.jinxu#gmail.com for a local snapshot (replace # with @).
    3. Shenlong has snapshotted the POC code for you. To support long-term maintenance, please consider donating. Thank you for your support.