Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed messages by replacing its signatures with a "standalone" or "timestamp" signature.
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Link | Tags |
---|---|
https://sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js/ | third party advisory exploit |
https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html#download=1 | third party advisory |
https://github.com/openpgpjs/openpgpjs/releases/tag/v4.2.0 | release notes |
https://github.com/openpgpjs/openpgpjs/pull/816 | third party advisory |
https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc | third party advisory patch |
http://packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attack.html | vdb entry third party advisory |