Spectrum Copy Data ManagementApplication · Ibm

CVE-2022-22354

HIGH · 7.5 CVSS v3.1 Published 2022-03-14
Fix available
A fix is available. Upgrade to 2.2.15 / 10.1.9.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
IBM Spectrum Protect Plus 10.1.0.0 through 10.1.9.2 and IBM Spectrum Copy Data Management 2.2.0.0 through 2.2.14.3 do not limit the length of a connection which could allow for a Slowloris HTTP denial of service attack to take place. This can cause the Admin Console to become unresponsive. IBM X-Force ID: 220485.

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 confidence

IBM Spectrum Protect Plus and Spectrum Copy Data Management fail to enforce connection length limits in their HTTP server, enabling a Slowloris attack where incomplete HTTP headers are sent sequentially to keep connections open and exhaust server resources, rendering the Admin Console unresponsive.

MitigationApply vendor patches (Spectrum Protect Plus 10.1.10+ or Spectrum Copy Data Management 2.2.15+) to add proper connection handling limits; alternatively, place a reverse proxy with DoS protection in front of the Admin Console.

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
Spectrum Copy Data ManagementApplication
Affected:>= 2.2.0.0, < 2.2.15
Spectrum Protect PlusApplication
Affected:>= 10.1.0, < 10.1.9.3

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Spectrum Protect Plus version
    Run 'dsmc q opt' or check the installation directory for version files. On Linux: /opt/tivoli/tsm/ directory. On Windows: Check registry or installation path.
    Affected if Version is >= 10.1.0 and < 10.1.9.3
  2. Identify IBM Spectrum Copy Data Management version
    Check the installation directory for version info. Look for version.properties or similar in the installation folder, or use the administrative web UI version display.
    Affected if Version is >= 2.2.0.0 and < 2.2.15
  3. Verify Admin Console HTTP service accessibility
    Check if port 9443 (default HTTPS) or port 9080 (default HTTP) for the admin console is exposed to network. Use 'netstat -an | grep -E '9080|9443'' or check firewall rules.
    Affected if Admin Console port is accessible from untrusted networks without a reverse proxy or WAF with DoS protection
  4. Monitor for connection exhaustion symptoms
    Use 'netstat -an | grep TIME_WAIT' or 'ss -s' to observe connection states. Check if many connections remain in CLOSE_WAIT or ESTABLISHED state with incomplete headers.
    Affected if Large number of incomplete HTTP connections accumulate, causing Admin Console unresponsiveness
  5. Review reverse proxy or load balancer configuration
    Inspect any proxy in front of the admin console for connection limiting, timeout settings, and DoS protection configuration.
    Affected if No reverse proxy with DoS protection exists, or existing proxy lacks connection timeout and request header limits

User is affected if either product version falls within the vulnerable range AND the Admin Console HTTP service is exposed without protective proxy or connection limits in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.15 / 10.1.9.3 or later
Fixed in 2.2.1510.1.9.3
Interim mitigation

Apply vendor patches (Spectrum Protect Plus 10.1.10+ or Spectrum Copy Data Management 2.2.15+) to add proper connection handling limits; alternatively, place a reverse proxy with DoS protection in front of the Admin Console.

Recommended fix High confidence

Spectrum Copy Data Management >= 2.2.15 or Spectrum Protect Plus >= 10.1.9.3

  1. Identify which IBM product is affected: Spectrum Copy Data Management or Spectrum Protect Plus
  2. For Spectrum Copy Data Management: Upgrade to version 2.2.15 or later
  3. For Spectrum Protect Plus: Upgrade to version 10.1.9.3 or later
  4. After upgrade, verify the Admin Console is responsive and functioning normally
  5. Monitor system logs to confirm the DoS vulnerability has been mitigated
Caveat Standard upgrade best practices apply - test in non-production environment first, backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spectrum Copy Data Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22354 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22354 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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