PrivateBin vulnerabilities

PrivateBin before version 2.0.5 has a vulnerability in Request::getRequestUri() which passes $_SERVER['REQUEST_URI'] through FILTER_SANITIZE_URL, not removing quotation marks, angle brackets, or apostrophes. The attacker-controlled value is then inserted into JSON-LD templates without JSON escaping, potentially allowing injection of data into application/ld+json responses.

PrivateBin is an online pastebin where the server has zero knowledge of pasted data. Prior to 2.0.5, AttachmentViewer.setAttachment in js/privatebin.js uses getAttachmentMimeType to accept attacker-controlled MIME types and uses getBlobUrl to create a same-origin blob before setting attachmentLink's href for the Download attachment link. The SVG-only sanitization branch updates only the preview blob, so text/html, image/svg, application/xhtml+xml, and text/xml attachments can remain active in the download blob. On an instance with fileupload = true and a weakened, stripped, or absent Content Security Policy, an anonymous attacker can create such an attachment, and a victim who opens the link in a new tab causes inline JavaScript to execute in the PrivateBin origin. The script can read origin-scoped local storage and issue same-origin requests, including requests to applications co-hosted on the same domain. This issue is fixed in version 2.0.5.

PrivateBin versions 1.7.7 through before 2.0.3 contain an unauthenticated Local File Inclusion in the template-switching feature. If templateselection is enabled, the server trusts the template cookie and includes the referenced PHP file, potentially allowing sensitive data disclosure or remote code execution. Fixed in version 2.0.3; workaround is to set templateselection = false.

PrivateBin is an online pastebin with zero knowledge of pasted data. Versions 1.7.7 through 2.0.1 allow persistent HTML injection via the unsanitized attachment filename (attachment_name) when attachments are enabled. An attacker can modify attachment_name before encryption so that, after decryption, arbitrary HTML is inserted unescaped near the file size hint, enabling redirects and site defacement and related phishing attacks. Script execution is normally blocked by the recommended CSP.