CVE-2020-4045 Information disclosure in SSB-DB
A bug in SSB-DB allows malicious peers to access decrypted private messages when used with SSB-Server, requiring an upgrade to fix.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-4045?
CVE-2020-4045 is a high-severity vulnerability in ssbc SSB-DB, published on 11 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
SSB-DB version 20.0.0 has an information disclosure vulnerability. The get() method is supposed to only decrypt messages when you explicitly ask it to, but there is a bug where it's decrypting any message that it can. This means that it is returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running [email protected] who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around get() to anonymous peers. This is fixed in version 20.0.1. Note that users of SSB-Server verion 16.0.0 should upgrade to 16.0.1 to get the fixed version of SSB-DB.
Weakness: CWE-200
Which versions are affected by CVE-2020-4045?
2 open source packages ship an affected version, including ssb-db. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
ssb-db npm | From 20.0.0 | 20.0.1 |
ssb-db npm | From 20.0.0 | 20.0.1 |
Products include Scuttlebutt Ssb-Db.
How do I fix CVE-2020-4045?
Upgrade ssb-db to 20.0.1 or later.
Is CVE-2020-4045 being exploited?
There is no known exploitation of CVE-2020-4045 in the wild and no public exploit code.
Sources
Also known as GHSA-mpgr-2cx9-327h.