CVE-2022-22346
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 Operations Center 8.1.0.000 through 8.1.13.xxx is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 220048.
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 · moderate confidenceIBM Spectrum Protect Operations Center versions 8.1.0.000 through 8.1.13.xxx are vulnerable to cross-site request forgery (CSRF). This allows attackers to trick authenticated users into unknowingly executing unauthorized actions by leveraging the trusted relationship between the user and the application.
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>= 8.1.0.000, < 8.1.14.000CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Locate IBM Spectrum Protect Operations Center installationIdentify whether the IBM Spectrum Protect Operations Center component is installed on the system. This is typically found on a dedicated server or management node running the IBM Spectrum Protect Plus component.Affected if Operations Center is installed and running
-
Determine installed Operations Center versionAccess the Operations Center web interface and navigate to the About or Version section, or use the dsmadmc command-line interface with appropriate credentials to query the server version. The version will display in format such as 8.1.x.xxx.Affected if Version falls within 8.1.0.000 through 8.1.13.xxx
-
Compare version to affected rangeVerify the exact version number against the vulnerable range: any version from 8.1.0.000 up to and including 8.1.13.xxx is affected. Versions 8.1.14.000 and later are not affected.Affected if Installed version is >= 8.1.0.000 and < 8.1.14.000
-
Check web interface exposureDetermine if the Operations Center web interface (typically on port 9080 or 443) is accessible from network locations where untrusted users could potentially submit requests. CSRF requires an authenticated user session.Affected if Web interface is accessible and users have active sessions
The environment is affected if IBM Spectrum Protect Operations Center is installed with a version between 8.1.0.000 and 8.1.13.xxx inclusive, and the web interface is accessible to users.
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 · scoped8.1.14.000
Apply the IBM patch for this vulnerability (upgrade to a fixed version beyond 8.1.13.xxx). Additionally, implement SameSite cookie attributes and anti-CSRF tokens as defense-in-depth measures.
IBM Spectrum Protect Operations Center 8.1.14.000
- 1. Review IBM Spectrum Protect Operations Center upgrade documentation before proceeding
- 2. Ensure you have a complete backup of your current configuration and data
- 3. Schedule a maintenance window for the upgrade process
- 4. Download IBM Spectrum Protect Operations Center version 8.1.14.000 or later from IBM Fix Central or your authorized IBM distribution channel
- 5. Stop all Spectrum Protect Operations Center services before upgrading
- 6. Run the upgrade installer for version 8.1.14.000
- 7. Verify the upgrade was successful by checking the Operations Center version information
- 8. Restart Spectrum Protect services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22346 — 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-22346 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