CVE-2020-5223
Privatebin vulnerability
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3.2 & v1.2.2. Admins are urged to upgrade to these versions to protect the affected users.
Affected products
Privatebin. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Privatebin 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.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- privatebin.info/news/v1.3.2-v1.2.2-release.html · Vendor Advisory
- github.com/PrivateBin/PrivateBin/commit/8d0ac336d23cd8c98e71d5f21cdadcae9c8a26e6 · Patch
- github.com/PrivateBin/PrivateBin/issues/554 · Third Party Advisory
- github.com/PrivateBin/PrivateBin/security/advisories/GHSA-8j72-p2wm-6738 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2020-5223
- cve.org/CVERecord?id=CVE-2020-5223
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.