Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

github логотип

GHSA-mpgr-2cx9-327h

Опубликовано: 11 июн. 2020
Источник: github
Github: Прошло ревью
CVSS3: 7.5

Описание

Information disclosure in SSB-DB

Impact

What kind of vulnerability is it? Who is impacted?

Servers running SSB-DB 20.0.0 (which is packaged with SSB-Server 16.0.0) must upgrade immediately.

There is no evidence that other SSB apps are vulnerable or that this problem has been exploited in the wild.

The get() method is supposed to only decrypt messages when you explicitly ask it to, but there's a bug where it's decrypting any message that it can. This means that it's returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 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.

Patches

Has the problem been patched? What versions should users upgrade to?

Yes, please upgrade to SSB-DB 20.0.1 (or SSB-Server 16.0.1) immediately.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

You may be able to disable the most obvious attack vector, SSB-OOO, by disabling the plugin, but you should upgrade immediately anyway.

For more information

If you have any questions or comments about this advisory, open an issue in SSB-DB

Пакеты

Наименование

ssb-db

npm
Затронутые версииВерсия исправления

= 20.0.0

20.0.1

EPSS

Процентиль: 54%
0.00316
Низкий

7.5 High

CVSS3

Дефекты

CWE-200

Связанные уязвимости

CVSS3: 7.5
nvd
больше 5 лет назад

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 SSB-DB@20.0.0 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.

EPSS

Процентиль: 54%
0.00316
Низкий

7.5 High

CVSS3

Дефекты

CWE-200