| Title | heinekingmedia StashCat における鍵管理のエラーに関する脆弱性 |
|---|---|
| Summary | heinekingmedia StashCat には、鍵管理のエラーに関する脆弱性が存在します。 |
| Possible impacts | 情報を取得される可能性があります。 |
| Solution | ベンダ情報および参考情報を参照して適切な対策を実施してください。 |
| Publication Date | July 31, 2017, midnight |
| Registration Date | Sept. 1, 2017, 11:46 a.m. |
| Last Update | Sept. 1, 2017, 11:46 a.m. |
| CVSS3.0 : 警告 | |
| Score | 6.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CVSS2.0 : 警告 | |
| Score | 4 |
|---|---|
| Vector | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| heinekingmedia GmbH |
| stashcat 0.0.80w まで (Web) |
| stashcat 0.0.86 まで (Desktop) |
| stashcat 1.7.5 まで (Android) |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年09月01日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | An issue was discovered in heinekingmedia StashCat through 1.7.5 for Android, through 0.0.80w for Web, and through 0.0.86 for Desktop. It uses RSA to exchange a secret for symmetric encryption of messages. However, the private RSA key is not only stored on the client but transmitted to the backend, too. Moreover, the key to decrypt the private key is composed of the first 32 bytes of the SHA-512 hash of the user password. But this hash is stored on the backend, too. Therefore, everyone with access to the backend database can read the transmitted secret for symmetric encryption, hence can read the communication. |
|---|---|
| Publication Date | Aug. 1, 2017, 11:29 p.m. |
| Registration Date | Jan. 26, 2021, 1:12 p.m. |
| Last Update | Nov. 21, 2024, 12:07 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:*:android:*:* | 1.7.5 | ||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:web:*:*:* | 0.0.80w | ||||
| Configuration3 | or higher | or less | more than | less than | |
| cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:desktop:*:*:* | 0.0.86w | ||||