CVE-2019-9153
Openpgpjs vulnerability
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.
Affected products
Openpgpjs. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Openpgpjs runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc · Patch
- packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attac · Third Party Advisory
- github.com/openpgpjs/openpgpjs/pull/816 · Third Party Advisory
- sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js/ · Exploit
- www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mai · Third Party Advisory
- github.com/openpgpjs/openpgpjs/releases/tag/v4.2.0
- nvd.nist.gov/vuln/detail/CVE-2019-9153
- cve.org/CVERecord?id=CVE-2019-9153
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.