CVE-2022-22354
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 · uneditedIBM 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 confidenceIBM 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.
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>= 2.2.0.0, < 2.2.15>= 10.1.0, < 10.1.9.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Spectrum Protect Plus versionRun '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
-
Identify IBM Spectrum Copy Data Management versionCheck 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
-
Verify Admin Console HTTP service accessibilityCheck 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
-
Monitor for connection exhaustion symptomsUse '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
-
Review reverse proxy or load balancer configurationInspect 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.
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 · scoped2.2.1510.1.9.3
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.
Spectrum Copy Data Management >= 2.2.15 or Spectrum Protect Plus >= 10.1.9.3
- Identify which IBM product is affected: Spectrum Copy Data Management or Spectrum Protect Plus
- For Spectrum Copy Data Management: Upgrade to version 2.2.15 or later
- For Spectrum Protect Plus: Upgrade to version 10.1.9.3 or later
- After upgrade, verify the Admin Console is responsive and functioning normally
- Monitor system logs to confirm the DoS vulnerability has been mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22354 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