CVE-2021-31475
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on affected installations of SolarWinds Orion Job Scheduler 2020.2.1 HF 2. Authentication is required to exploit this vulnerability. The specific flaw exists within the JobRouterService WCF service. The issue is due to the WCF service configuration, which allows a critical resource to be accessed by unprivileged users. An attacker can leverage this vulnerability to execute code in the context of an administrator. Was ZDI-CAN-12007.
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 confidenceThis is a WCF (Windows Communication Foundation) service misconfiguration in SolarWinds Orion Job Scheduler that allows authenticated but unprivileged users to access critical administrative resources through the JobRouterService. The vulnerability stems from insufficient authorization enforcement in the WCF service configuration, enabling remote attackers to execute arbitrary code in the context of an administrator after authentication.
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= 2020.2.1CVSS 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.
-
Confirm SolarWinds Orion Job Scheduler versionCheck the installed version of SolarWinds Orion Job Scheduler. This may be found in the program's About page, registry, or the installation directory. Compare against version 2020.2.1.Affected if The installed version is exactly 2020.2.1.
-
Locate the WCF service configuration filesFind the web.config or app.config file for the SolarWinds Orion Job Scheduler installation. These are typically located in the installation directory or the web application's root directory.Affected if The configuration file exists and contains WCF service configuration for JobRouterService.
-
Inspect JobRouterService authorization settingsIn the configuration file, locate the <system.serviceModel> section and examine the <authorization> or <serviceAuthorization> elements for the JobRouterService endpoint. Check whether role-based or claim-based authorization is explicitly configured.Affected if No explicit role-based or claim-based authorization rules are defined for the JobRouterService, or the authorization is set to allow authenticated users without privilege restrictions.
-
Verify endpoint binding and security settingsExamine the <bindings> and <security> configuration for the JobRouterService endpoint. Determine if authentication is required and what authentication mode is in use (e.g., Windows, Certificate, or None).Affected if The endpoint permits authenticated but unprivileged users to access the service without additional privilege checks.
A user is affected if they have SolarWinds Orion Job Scheduler version 2020.2.1 running with the JobRouterService exposed and the WCF authorization configured to allow authenticated but unprivileged users access to administrative resources.
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 dataConfigure proper role-based and claim-based authorization in the WCF service configuration (web.config or app.config) to enforce least-privilege access controls, ensuring unprivileged users cannot access critical administrative resources or execute privileged operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31475 — 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-2021-31475 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