CVE-2020-25617
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 · uneditedAn issue was discovered in SolarWinds N-Central 12.3.0.670. The AdvancedScripts HTTP endpoint allows Relative Path Traversal by an authenticated user of the N-Central Administration Console (NAC), leading to execution of OS commands as root.
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 confidenceSolarWinds N-Central version 12.3.0.670 contains a Relative Path Traversal vulnerability in the AdvancedScripts HTTP endpoint. An authenticated user of the N-Central Administration Console can manipulate path traversal sequences to access arbitrary files and execute OS commands with root privileges.
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= 12.3.0.670CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SolarWinds N-Central is installedLocate the N-Central installation directory or check system services for 'n-central' or 'SolarWinds N-Central' serviceAffected if N-Central is not present on the system, then not affected by this CVE
-
Check the exact N-Central versionAccess the N-Central Administration Console and navigate to Help > About, or check the version information in the installation directoryAffected if The installed version is NOT exactly 12.3.0.670, then not affected by this specific CVE (only this exact version is vulnerable)
-
Confirm AdvancedScripts feature is enabledLog into the N-Central Administration Console and navigate to Administration > Scripts > AdvancedScripts, or check the configuration file for AdvancedScripts module statusAffected if AdvancedScripts is disabled or not configured, the path traversal in this endpoint cannot be exploited
-
Verify the AdvancedScripts HTTP endpoint is accessibleCheck if port 443 or 80 is open and responding for the N-Central server, and confirm the /AdvancedScripts endpoint is reachableAffected if The HTTP endpoint is not exposed or accessible, the vulnerability cannot be triggered even on the affected version
You are affected only if SolarWinds N-Central version 12.3.0.670 is installed, AdvancedScripts is enabled, and the AdvancedScripts HTTP endpoint is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied patch or upgrade to a fixed version of SolarWinds N-Central. If immediate patching is not possible, restrict NAC access to trusted administrators only and monitor for suspicious path traversal patterns in AdvancedScripts requests.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-25617 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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