dbcve.org
N CentralApplication · N Able

CVE-2024-28200

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2024.2 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 an authentication bypass of the user interface. This vulnerability is present in all deployments of N-central prior to 2024.2. This vulnerability was discovered through internal N-central source code review and N-able has not observed any exploitation in the wild.

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 · moderate confidence

This is an authentication bypass vulnerability in N-central's user interface that allows attackers to gain unauthorized access to the management console without valid credentials. The critical CVSS 9.8 score indicates this bypass likely enables complete compromise of the management interface, potentially giving attackers full control over the monitored infrastructure.

MitigationUpgrade N-central to version 2024.2 or later to address this authentication bypass vulnerability. Organizations should prioritize this upgrade given the critical severity and potential for complete system compromise.

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.2

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
High

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

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. Confirm N-central product installation
    Verify the target system is running N Able N-central by checking system inventory, software listings, or the product's about/version interface
    Affected if The system is not running N-central or the version cannot be determined
  2. Check installed N-central version
    Access the N-central version information through the system configuration panel, about page, or version check mechanism provided by the software
    Affected if The installed version is any release prior to 2024.2 (versions 2024.1, 2023.x, earlier)
  3. Identify management console accessibility
    Determine if the N-central management console web interface is network-accessible and note its exposure level (internal only, VPN-required, or internet-facing)
    Affected if The management console is exposed to untrusted networks without authentication barriers
  4. Review authentication events for unauthorized access
    Examine N-central authentication logs, session records, or audit trails for any access attempts, sessions, or administrative actions that occurred without valid credentials
    Affected if There are authentication events, sessions, or admin actions that cannot be attributed to legitimate users

You are affected if the system runs N Able N-central version below 2024.2 and the management console is accessible (especially externally), regardless of whether you see evidence of exploitation.

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.2 or later
Fixed in 2024.2
Interim mitigation

Upgrade N-central to version 2024.2 or later to address this authentication bypass vulnerability. Organizations should prioritize this upgrade given the critical severity and potential for complete system compromise.

Recommended fix High confidence

2024.2

  1. Back up the current N-central server configuration and database before initiating any upgrade
  2. Log in to the N-able customer portal (me.n-able.com) or partner portal to download the N-central 2024.2 upgrade package
  3. Review the official N-central upgrade documentation at documentation.n-able.com for version-specific upgrade procedures
  4. Apply the upgrade to the N-central server following the documented upgrade path for your current version
  5. After upgrade completion, verify the N-central server is running version 2024.2 by checking the server UI or about page
  6. Confirm that the web interface is accessible and the authentication mechanism is functioning correctly
Caveat Review N-able release notes for 2024.2 for any configuration or feature changes that may affect your deployment

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

Fix this in N Central Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28200 — 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-28200 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