GHSA-5875-p652-2ppm CVE-2022-0762
Exposure of Resource to Wrong Sphere in microweber
Medium
Packagist
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.65%
- Chance of exploitation in the next 30 days. Higher than 51.32% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
1.3.0- Upgrade microweber/microweber to this version or later
Description
Exposure of Resource to Wrong Sphere in microweber prior to 1.3 allows users to add deleted products to a cart and buy it.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| microweber/microweber | < 1.3.0 |
1.3.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
microweber/microweber Packagist → 1.3.0
- composer
composer require microweber/microweber:^1.3.0
Severity breakdown
CVSS 3.1 4.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Weakness
CWE-668: Exposure of Resource to Wrong Sphere
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
CWE-863: 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 to prevent it
- Architecture and Design: 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) [REF-229] 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.
- Architecture and Design: 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 [REF-7].
- Architecture and Design: 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 [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vv4x-qcpq-wgrg Microweber vulnerable to Path Traversal | High | Also affects microweber/microweber |
| GHSA-6w5w-jx4x-vjvw Microweber Cross-site Scripting vulnerability | Medium | Also affects microweber/microweber |
| GHSA-5jg5-xqfw-rv92 Microweber has a Cross-site Scripting vulnerability | Medium | Also affects microweber/microweber |
| GHSA-2x2j-3c2v-g3c2 Microweber XSS Vulnerability in the homepage Endpoint | High | Also affects microweber/microweber |
| GHSA-mvj3-hc7j-vp74 Microweber has Reflected XSS Vulnerability in the layout Parameter | Medium | Also affects microweber/microweber |
| GHSA-8357-fjvx-xrm8 Microweber has Reflected XSS Vulnerability in the id Parameter | Medium | Also affects microweber/microweber |
| GHSA-782f-gxj5-xvqc Microweber Has Stored XSS Vulnerability in User Profile Fields | High | Also affects microweber/microweber |
| GHSA-j64v-xh5w-8hqj Microweber CMS API has authenticated local file inclusion vulnerability | High | Also affects microweber/microweber |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor