microweber/microweber: Incorrect Authorization
CVE-2022-1631 is a high-severity incorrect authorization vulnerability in microweber/microweber from Microweber, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 1.2.15 as the first without the flaw, so updating microweber/microweber to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 8.85% chance of exploitation within 30 days, which is in the top 4.72% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update microweber/microweber to 1.2.15 or a later version.
- Update Microweber to 1.2.15 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microweber | microweber/microweber | before 1.2.15 | 1.2.15 |
| Microweber | Microweber | before 1.2.15 | 1.2.15 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.0 | 6.8 | Medium | CNA (huntr.dev) |
| CVSS 2.0 | 6.8 | Medium | NVD |
Official description
Users Account Pre-Takeover or Users Account Takeover. in GitHub repository microweber/microweber prior to 1.2.15. Victim Account Take Over. Since, there is no email confirmation, an attacker can easily create an account in the application using the Victim’s Email. This allows an attacker to gain pre-authentication to the victim’s account. Further, due to the lack of proper validation of email coming from Social Login and failing to check if an account already exists, the victim will not identify if an account is already existing. Hence, the attacker’s persistence will remain. An attacker would be able to see all the activities performed by the victim user impacting the confidentiality and attempt to modify/corrupt the data impacting the integrity and availability factor. This attack becomes more interesting when an attacker can register an account from an employee’s email address. Assuming the organization uses G-Suite, it is much more impactful to hijack into an employee’s account.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/microweber/microweber/commit/c162dfffb9bfd264d232aaaf5bb3daee16a3cb38Third Party Advisory
- huntr.dev/bounties/5494e258-5c7b-44b4-b443-85cff7ae0ba4Exploit, Third Party Advisory
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/167376/Microweber-CMS-1.2.15-Account-Takeover.htmlExploit, Third Party Advisory, VDB Entry
Other vulnerabilities in microweber/microweber
- 7.5 High severity
Recent Incorrect Authorization vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 9.8 Critical severity
- 10.0 Critical severity
Spotted an error? Tell us.