PrivateBin 1.3
PrivateBin 1.3
The PrivateBin 1.3 reached end of service life on Apr 9, 2022 — PrivateBin no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your PrivateBin 1.3 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- privatebin
- release
- 1.3
- product Label
- PrivateBin
- release Label
- 1.3
- codename
- lts
- latest Version
- 1.3.5
- release Date
- 2019-07-09
- maintained
- source Url
- https://endoflife.date/privatebin
Lifecycle Dates
- End of Service Life
- Apr 9, 2022
- Last OEM Support
- Apr 9, 2022
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for PrivateBin 1.3 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for PrivateBin 1.3?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for PrivateBin 1.3 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
PrivateBin 1.3 Support: Frequently Asked Questions
Is the PrivateBin 1.3 still supported?
PrivateBin ended support for the PrivateBin 1.3 on Apr 9, 2022 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the PrivateBin 1.3 end of service life (EOSL) date?
PrivateBin lists the end of service life for the PrivateBin 1.3 as Apr 9, 2022.
Can I keep using the PrivateBin 1.3 after its EOSL date?
Yes. EOSL means PrivateBin stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the PrivateBin 1.3 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting PrivateBin 1.3
2 published CVEs affect the PrivateBin 1.3, including 1 rated critical or high severity. PrivateBin no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2022-24833 | HIGH | 8.2 | Apr 11, 2022 | PrivateBin is minimalist, open source online pastebin clone where the server has zero knowledge of pasted data. In PrivateBin < v1.4.0 a cross-site scripting (XSS) vulnerability was found. The vulnerability is present in all versions from v0.21 of the project, which was at the time still called ZeroBin. The issue is caused by the fact that SVGs can contain JavaScript. This can allow an attacker to execute code, if the user opens a paste with a specifically crafted SVG attachment, and interacts w |
| CVE-2020-5223 | MEDIUM | 6.1 | Jan 23, 2020 | 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. |