CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalResearch in progress

CVE-2020-10148 remediation guide

SolarWinds Orion

The SolarWinds Orion API is vulnerable to an authentication bypass that could allow a remote attacker to execute API commands. This vulnerability could allow a remote attacker to bypass authentication and execute API commands which may result in a compromise of the SolarWinds instance. SolarWinds Orion Platform versions 2019.4 HF 5, 2020.2 with no hotfix installed, and 2020.2 HF 1 are affected.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductSolarWinds Orion
Affected versions2019.4 HF 5, 2020.2 without hotfix, 2020.2 HF 1, 2019.4, 2020.2.1, 2020.2
Fixed versionsNo verified fixed-version field is available yet
Priority basisImmediate · CVSS 9.8 · EPSS 92.0%
01

Identify the affected asset

Confirm whether SolarWinds Orion is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 2019.4 HF 5, 2020.2 without hotfix, 2020.2 HF 1, 2019.4, 2020.2.1, 2020.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.