POJIA破甲
地图 / Slack DTLS uses a private key that is in the public domain, which may lead to SRTP stream hijack

Slack DTLS uses a private key that is in the public domain, which may lead to SRTP stream hijack

密码学缺陷 / Use of Hard-coded Cryptographic Key / #531032

厂商
Slack
严重程度
中危 · CVSS 8.7
赏金
$2,000
弱点
Use of Hard-coded Cryptographic Key
研究员
@sandrogauci
披露日期
2020-03-12
资产
slack.com
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(3135 字符中的一小部分)
The Janus server in use by Slack is configured using a certificate and private key that were previously distributed by default. This certificate is used to authenticate the DTLS _connection_ which is later used to exchange keys for the SRTP stream. As a result, the confidentiality of the WebRTC …
原文中的代码
openssl x509 -noout -fingerprint -sha256 -inform pem -in janus-cert1.crt 
SHA256 Fingerprint=C5:5F:DA:7D:84:47:B1:BF:6B:55:16:62:48:31:3E:D3:F1:7B:25:89:92:4A:4B:4D:4D:D9:D5:AF:EA:D8:15:44

默认不展示报告全文。以上为简短摘录,完整复现过程请阅读原文。版权归研究员与 Slack 所有。

时间线

  • 报告提交
  • 公开披露
阅读 HackerOne 原文 ↗作者 @sandrogauci · 版权归作者与 Slack 所有

同类报告

Infromation Disclosure To Use of Hard-coded Cryptographic KeyReddit · 2024-02-06Sauce Labs API key unencrypted in an old commitRuby on Rails · 2024-10-08Exposure of Hard-coded Private Keys and Credentials in curl Source Repository (CWE-321)curl · 2025-08-12`Cody trolled us all` h1-702 CTF write-up50m-ctf · —