Skip to content

GHSA-wxw9-6pv9-c3xc CVE-2024-48929

Umbraco CMS Has Incomplete Server Termination During Explicit Sign-Out

Medium NuGet
Severity
4.2 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.27%
Chance of exploitation in the next 30 days. Higher than 19.07% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-384 Session Fixation
Fix
13.5.2
Upgrade Umbraco.CMS to this version or later

Description

Impact

During an explicit sign-out, the server session is not fully terminated.

Affected versions

NuGet

PackageVulnerableFixed in
Umbraco.CMS
>= 13.0.0, < 13.5.2
13.5.2
Umbraco.CMS
>= 10.0.0, < 10.8.7
10.8.7

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 → 13.5.2

dotnet
dotnet add package Umbraco.CMS --version 13.5.2

Severity breakdown

CVSS 3.1 4.2

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-384: Session Fixation

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

How to prevent it
  • Architecture and Design: Invalidate any existing session identifiers prior to authorizing a new user session.
  • Architecture and Design: For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
  • Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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