CVE-2022-2815 Insecure Storage of Sensitive Information in publify/publify
Attackers can access sensitive information stored insecurely in the Publify blog platform, potentially exposing user data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-2815?
CVE-2022-2815 is a medium-severity vulnerability in publify/publify, published on 14 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Insecure Storage of Sensitive Information in GitHub repository publify/publify prior to 9.2.10.
Weakness: CWE-922
Which versions are affected by CVE-2022-2815?
3 open source packages ship an affected version, including publify_core and publify. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
publify_core RubyGems | All versions | 9.2.10 |
publify_core RubyGems | All versions | 9.2.10 |
publify Bitnami | All versions | 9.2.10 |
Products include Publify Project Publify.
How do I fix CVE-2022-2815?
Upgrade publify_core to 9.2.10 or later.
Is CVE-2022-2815 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2815 exists.
Other vulnerabilities in publify/publify
- CVE-2022-1810 Authorization Bypass Through User-Controlled Key in publify/publify
- CVE-2022-1811 Unrestricted Upload of File with Dangerous Type in publify/publify
- CVE-2022-1553 Leaking password protected articles content due to improper access control in publify/publify
- CVE-2023-0299 Improper Input Validation in publify/publify
- CVE-2023-0569 Weak Password Requirements in publify/publify
Sources
Also known as BIT-publify-2022-2815, GHSA-79wq-g4v9-gfj4.