Security Resilience

CVE-2023-33224

Solarwinds Platform ≤ 2023.3.0

Published
26 July 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.028 86th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-33224 is a high-severity Incorrect Behavior Order (CWE-696) vulnerability in Solarwinds Solarwinds Platform. Its CVSS base score is 7.2 (High).

Operationally, ranked in the top 14% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

The SolarWinds Platform was susceptible to the Incorrect Behavior Order Vulnerability. This vulnerability allows users with administrative access to SolarWinds Web Console to execute arbitrary commands with NETWORK SERVICE privileges.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-52606Same product: Solarwinds Solarwinds Platform
CVE-2024-29004Same product: Solarwinds Solarwinds Platform
CVE-2024-28999Same product: Solarwinds Solarwinds Platform
CVE-2024-45710Same product: Solarwinds Solarwinds Platform
CVE-2024-29001Same product: Solarwinds Solarwinds Platform
CVE-2023-33229Same product: Solarwinds Solarwinds Platform
CVE-2023-33225Same product: Solarwinds Solarwinds Platform
CVE-2023-35188Same product: Solarwinds Solarwinds Platform
CVE-2024-29000Same product: Solarwinds Solarwinds Platform
CVE-2023-3622Same product: Solarwinds Solarwinds Platform

Affected Assets

solarwinds
solarwinds platform
≤ 2023.3.0

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates security in the SDLC including secure coding, requirements, checkpoints, testing and developer training that can catch and stop incorrect behavior ordering before it reaches production, but this is only a minority slice of the weakness class (most instances arise from implementation errors not governed by process mandates).

blocks

Secure system architecture and engineering principles require proper ordering of design and implementation steps.

prevents

Secure coding standards enforce correct execution order of security-critical operations.

finds

Security testing can detect ordering flaws but does not prevent them during development.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-696, a class-level weakness, and none of its children carries one either.

References