GHSA-7x74-h8cw-qhxq CVE-2023-49278
Brute force exploit can be used to collect valid usernames
- Severity
- 0.0 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.50%
- Chance of exploitation in the next 30 days. Higher than 42.89% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
8.18.10- Upgrade Umbraco.CMS to this version or later
Description
Impact
A brute force exploit that can be used to collect valid usernames is possible.
Explanation of the vulnerability
It's a brute force exploit that can be used to collect valid usernames by using the “forgot password” function when trying to log into the Backoffice. If the username/email is known, it is easier to find the corresponding password. If an email address that was already used and registered by a user, is provided as an input, the server internal processing time takes longer. If the email address does not exist in the database of the registered users, the server would respond immediately.
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.1 |
10.8.1 |
| Umbraco.CMS | >= 11.0.0, < 12.3.4 |
12.3.4 |
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:N/UI:N/S:U/C:N/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
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