Vaultive Office 365 Security における暗号強度に関する脆弱性
| Title |
Vaultive Office 365 Security における暗号強度に関する脆弱性
|
| Summary |
Vaultive Office 365 Security には、暗号強度に関する脆弱性が存在します。
|
| Possible impacts |
情報を取得される、およびサービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution |
ベンダ情報および参考情報を参照して適切な対策を実施してください。 |
| Publication Date |
May 4, 2017, midnight |
| Registration Date |
June 9, 2017, 3:37 p.m. |
| Last Update |
June 9, 2017, 3:37 p.m. |
|
CVSS3.0 : 緊急
|
| Score |
9.1
|
| Vector |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
|
CVSS2.0 : 警告
|
| Score |
6.4
|
| Vector |
AV:N/AC:L/Au:N/C:P/I:N/A:P |
Affected System
| Vaultive, Inc. |
|
Vaultive Office 365 Security 4.5.21 未満
|
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
その他
Change Log
| No |
Changed Details |
Date of change |
| 0 |
[2017年06月09日]
掲載 |
Feb. 17, 2018, 10:37 a.m. |
NVD Vulnerability Information
CVE-2017-7229
| Summary |
PGP/MIME encrypted messages injected into a Vaultive O365 (before 4.5.21) frontend via IMAP or SMTP have their Content-Type changed from 'Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="abc123abc123"' to 'Content-Type: text/plain' - this results in the encrypted message being structured in such a way that most PGP/MIME-capable mail user agents are unable to decrypt it cleanly. The outcome is that encrypted mail passing through this device does not work (Denial of Service), and a common real-world consequence is a request to resend the mail in the clear (Information Disclosure).
|
| Publication Date |
May 4, 2017, 5:59 a.m. |
| Registration Date |
Jan. 26, 2021, 1:28 p.m. |
| Last Update |
Nov. 21, 2024, 12:31 p.m. |
Affected software configurations
| Configuration1 |
or higher |
or less |
more than |
less than |
| cpe:2.3:a:vaultive:office_365_security:4.5.19:*:*:*:*:*:*:* |
|
|
|
|
Related information, measures and tools
Common Vulnerabilities List