CVE-2022-1811 Unrestricted Upload of File with Dangerous Type in publify/publify
Attackers can upload malicious files to the Publify blog platform, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-1811?
CVE-2022-1811 is a critical vulnerability in publify/publify, published on 23 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.
Weakness: CWE-434
Which versions are affected by CVE-2022-1811?
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.9 |
publify_core RubyGems | All versions | 9.2.9 |
publify Bitnami | All versions | 9.2.9 |
Products include Publify Project Publify.
How do I fix CVE-2022-1811?
Upgrade publify_core to 9.2.9 or later.
Is CVE-2022-1811 being exploited?
There is no known exploitation of CVE-2022-1811 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-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
- CVE-2022-1812 Integer Overflow or Wraparound in publify/publify
Sources
Also known as BIT-publify-2022-1811, GHSA-3hwx-c6cp-q972.