Mailvelope prior to 3.3.0 allows private key operations without user interaction via its client-API. By modifying an URL parameter in Mailvelope, an attacker is able to sign (and encrypt) arbitrary messages with Mailvelope, assuming the private key password is cached. A second vulnerability allows an attacker to decrypt an arbitrary message when the GnuPG backend is used in Mailvelope.
References
Link | Resource |
---|---|
https://github.com/mailvelope/mailvelope/blob/master/Changelog.md#v330 | Release Notes Third Party Advisory |
https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.pdf?__blob=publicationFile&v=3 | Exploit Third Party Advisory |
https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html | Third Party Advisory |
Configurations
Information
Published : 2019-07-09 14:15
Updated : 2022-04-18 09:56
NVD link : CVE-2019-9149
Mitre link : CVE-2019-9149
JSON object : View
Products Affected
mailvelope
- mailvelope