CVE-2022-0574 Improper Access Control in publify/publify
Attackers can bypass access controls to read or modify data in the Publify blog application.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0574?
CVE-2022-0574 is a medium-severity missing authorization vulnerability in publify/publify, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Improper Access Control in GitHub repository publify/publify prior to 9.2.8.
Which versions are affected by CVE-2022-0574?
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.8 |
publify_core RubyGems | All versions | 9.2.8 |
publify Bitnami | All versions | 9.2.8 |
Products include Publify Project Publify.
How do I fix CVE-2022-0574?
Upgrade publify_core to 9.2.8 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-0574 being exploited?
There is no known exploitation of CVE-2022-0574 in the wild and no public exploit code.
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-0574, GHSA-79m3-q3wh-c3qm.