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.html | 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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2019-07-09T20:45:39
Updated: 2019-08-29T16:13:55
Reserved: 2019-02-25T00:00:00
Link: CVE-2019-9149
JSON object: View
NVD Information
Status : Analyzed
Published: 2019-07-09T21:15:11.333
Modified: 2022-04-18T16:56:49.047
Link: CVE-2019-9149
JSON object: View
Redhat Information
No data.