dbcve.org
N CentralApplication · N Able

CVE-2024-5322

CRITICAL · 9.1 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2024.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The N-central server is vulnerable to session rebinding of already authenticated users when using Entra SSO, which can lead to authentication bypass. This vulnerability is present in all Entra-supported deployments of N-central prior to 2024.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

N-central server contains a session rebinding vulnerability in its Entra SSO integration that allows attackers to hijack or rebind sessions of already authenticated users, enabling authentication bypass. The flaw allows an attacker to potentially take over legitimate user sessions without knowing their credentials. This is a critical authentication mechanism flaw present in all Entra-supported deployments prior to version 2024.3.

MitigationUpgrade N-central to version 2024.3 or later to remediate this vulnerability. If immediate upgrade is not possible, consider disabling Entra SSO and enforcing alternative authentication methods until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N CentralApplication
Affected:< 2024.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify N-central installation
    Locate the N-central server in your environment and confirm it is running. Check for N-central service processes or installation directories typically found in standard program locations.
    Affected if N-central server is deployed in the environment
  2. Check N-central version
    Access the N-central server's administration interface or check the software version through the built-in about/versions page in the N-central UI, or use system inventory tools if available.
    Affected if The installed version is any version prior to 2024.3 (e.g., 2024.2.x, 2024.1.x, earlier releases)
  3. Verify Entra SSO is configured
    Check the N-central authentication settings or SSO configuration panel to determine if Entra SSO integration is enabled. Look for Microsoft Entra ID (formerly Azure AD) SSO settings.
    Affected if Entra SSO integration is enabled and configured in N-central

You are affected if N-central server is running any version prior to 2024.3 AND Entra SSO integration is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2024.3 or later
Fixed in 2024.3
Interim mitigation

Upgrade N-central to version 2024.3 or later to remediate this vulnerability. If immediate upgrade is not possible, consider disabling Entra SSO and enforcing alternative authentication methods until the patch can be applied.

Recommended fix Moderate confidence

N-central 2024.3

  1. Download N-central version 2024.3 from the official N-able customer portal (me.n-able.com)
  2. Review the N-central 2024.3 release notes for Entra SSO configuration changes
  3. Before upgrading, backup the current N-central database and configuration
  4. Ensure the N-central server meets all prerequisites for version 2024.3
  5. Perform the upgrade following the standard N-central upgrade procedure documented at documentation.n-able.com
  6. After upgrade, verify Entra SSO configuration is functioning correctly
  7. Test authentication flow to confirm the session rebinding vulnerability is resolved
Caveat Review release notes for any Entra SSO configuration changes that may require adjustment during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data