GHSA-335x-5wcm-8jv2 CVE-2023-48227
Backoffice User can bypass "Publish" restriction
Medium
NuGet
- Severity
- 0.0 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.41%
- Chance of exploitation in the next 30 days. Higher than 35.13% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-863 Incorrect Authorization
- Fix
8.18.10- Upgrade Umbraco.CMS to this version or later
Description
Impact
Backoffice users with send for approval permission but not publish permission are able to publish in some scenarios.
Explanation of the vulnerability
Backoffice users without permission to publish content, but only to send for approval, can bypass the restriction by modifying the request body of the "Send for Approval" request.
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Umbraco.CMS | >= 8.0.0, < 8.18.10 |
8.18.10 |
| Umbraco.CMS | >= 9.0.0, < 10.8.0 |
10.8.0 |
| Umbraco.CMS | >= 11.0.0, < 12.3.0 |
12.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.
Umbraco.CMS NuGet → 8.18.10
- dotnet
dotnet add package Umbraco.CMS --version 8.18.10
Severity breakdown
CVSS 3.1 0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- None
Weakness
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-wr57-hqmp-fgvh Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion | High | Also affects Umbraco.Cms |
| GHSA-vr9v-27gg-qgx4 Umbraco.Cms: XSS/HTML Injection in Umbraco Backoffice confirmation dialog | Medium | Also affects Umbraco.Cms |
| GHSA-2qjj-h6wp-c7h7 Umbraco.Cms: Open Redirect Vulnerability in Surface Controllers | Medium | Also affects Umbraco.Cms |
| GHSA-rhcg-3h8r-v6vp Umbraco Affected by Vertical Privilege Escalation via Missing Authorization Checks | High | Also affects Umbraco.Cms |
| GHSA-vrqc-59mw-qqg7 Umbraco has Stored XSS in UFM Rendering Pipeline via Permissive DOMPurify Attribute Filtering | Medium | Also affects Umbraco.Cms |
| GHSA-fpvf-fvp5-996r Umbraco Backoffice API Allows Unauthorized Modification of Domain Data | Medium | Also affects Umbraco.Cms |
| GHSA-54mj-vcvj-q3v5 Umbraco CMS has an arbitrary file upload vulnerability | Critical | Also affects Umbraco.Cms |
| GHSA-hfv2-pf68-m33x Umbraco Vulnerable to Improper File Access and Credential Exposure in Dictionary Import Functionality | Medium | Also affects Umbraco.Cms |
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