CVE-2017-7229

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

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

Los mensajes encriptados PGP/MIME inyectados en un frontend Vaultive Office 365 (anterior a 4.5.21) a través de IMAP o SMTP modifican su Content-Type de 'Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="abc123abc123" to 'Content-Type: text/plain' Esto hace que el mensaje encriptado esté estructurado de tal manera que la mayoría de los agentes de correo PGP/MIME no pueden descifrarlo de forma limpia. El resultado es que el correo cifrado que pasa a través de este dispositivo no funciona (denegación de servicio), y una consecuencia común en el mundo real es que se produce una solicitud para volver a enviar el correo en claro (divulgación de información).