LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4469: IBM Spectrum Protect Plus 10.1.0 through 10.1.5 could allow a remote attacker to execute arbitrary code on...

IBM Spectrum Protect Plus 10.1.0 through 10.1.5 could allow a remote attacker to execute arbitrary code on the system. By using a specially crafted HTTP command, an attacker could exploit this vulnerability to execute arbitrary command on the system. This vulnerability is due to an incomplete fix for CVE-2020-4211. IBM X-Force ID: 181724.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-4469 is a high-severity remote code execution issue in IBM Spectrum Protect Plus 10.1.0 through 10.1.5. A remote attacker could use a specially crafted HTTP command to run arbitrary commands on the system. The source says this resulted from an incomplete fix for CVE-2020-4211.

Executive priority

Treat this as a high-priority remediation item for backup and recovery infrastructure. Compromise of Spectrum Protect Plus could affect sensitive backup data and operational recovery capability. Prioritize internet-exposed or broadly reachable deployments first.

Technical view

The vulnerability affects IBM Spectrum Protect Plus versions 10.1.0 through 10.1.5. It is network reachable, requires no privileges or user interaction, but has high attack complexity. Successful exploitation can compromise confidentiality, integrity, and availability. IBM assigns X-Force ID 181724 and CVSS 3.0 score 8.1.

Likely exposure

Exposure is likely limited to organizations running IBM Spectrum Protect Plus 10.1.0 through 10.1.5, especially where the vulnerable HTTP-accessible service is reachable from untrusted networks. The bundle does not identify affected cloud services, appliances beyond this product, or later versions.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked as CISA KEV. Exploitation is remote and unauthenticated according to CVSS, but attack complexity is high. Tenable and IBM references indicate public vulnerability documentation exists, not necessarily public weaponization.

Researcher notes

Key constraints are the affected version range, HTTP command vector, and incomplete CVE-2020-4211 fix lineage. Evidence provided does not include exploit details, affected endpoint names, or precise fixed versions, so validation should rely on IBM advisory guidance and asset version checks.

Mitigation direction

  • Inventory IBM Spectrum Protect Plus deployments and confirm exact versions.
  • Apply IBM's official remediation for CVE-2020-4469 from the IBM advisory.
  • Restrict network access to Spectrum Protect Plus HTTP interfaces to trusted administrators.
  • Review exposure created by any earlier CVE-2020-4211 remediation assumptions.
  • Monitor IBM and X-Force pages for updated guidance.

Validation and detection

  • Verify no production instance runs Spectrum Protect Plus 10.1.0 through 10.1.5.
  • Confirm the IBM advisory-recommended fix level is installed.
  • Check whether Spectrum Protect Plus HTTP services are internet-reachable.
  • Review logs for unusual HTTP requests and unexpected command execution indicators.
  • Document compensating controls where immediate remediation is delayed.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-4469 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/A:H/I:H/UI:N/S:U/PR:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.0HighCVSS:3.0/A:H/I:H/UI:N/S:U/PR:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.1High
CVSS 3.0 vector shape for CVE-2020-4469Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/A:H/I:H/UI:N/S:U/PR:N/AC:H/C:H/AV:N/E:U/RC:C/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMSpectrum Protect Plus10.1.0, 10.1.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.