Vaultive O365 up to 4.5.21 IMAG/SMTP PGP/MIME Message inadequate encryption

Summaryinfo

A vulnerability, which was classified as critical, has been found in Vaultive O365 up to 4.5.21. The affected element is an unknown function of the component IMAG/SMTP. This manipulation as part of PGP/MIME Message causes inadequate encryption. This vulnerability appears as CVE-2017-7229. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Vaultive O365 up to 4.5.21. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component IMAG/SMTP. The manipulation as part of a PGP/MIME Message leads to a inadequate encryption vulnerability. The CWE definition for the vulnerability is CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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).

The bug was discovered 08/04/2017. The weakness was presented 05/03/2017 (Website). It is possible to read the advisory at gist.github.com. This vulnerability is known as CVE-2017-7229 since 03/22/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Vaultive

Name

• O365

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.5.13
• 4.5.14
• 4.5.15
• 4.5.16
• 4.5.17
• 4.5.18
• 4.5.19
• 4.5.20
• 4.5.21

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion