Spectrum Protect Plus Container Backup And RestoreApplication · Ibm
CVE-2022-22472
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 Container Backup and Restore (10.1.5 through 10.1.10.2 for Kubernetes and 10.1.7 through 10.1.10.2 for Red Hat OpenShift) could allow a remote attacker to bypass IBM Spectrum Protect Plus role based access control restrictions, caused by improper disclosure of session information. By retrieving the logs of a container an attacker could exploit this vulnerability to bypass login security of the IBM Spectrum Protect Plus server and gain unauthorized access based on the permissions of the IBM Spectrum Protect Plus user to the vulnerable Spectrum Protect Plus server software. IBM X-Force ID: 225340.
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 Container Backup and Restore contains a vulnerability where session information is improperly disclosed through container logs. An attacker who can retrieve container logs can obtain session tokens, enabling them to bypass role-based access control restrictions and gain unauthorized access to the Spectrum Protect Plus server with the permissions of the compromised user.
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 Protect Plus Container Backup And RestoreApplication
>= 10.1.5, < 10.1.11>= 10.1.7, < 10.1.11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Determine your installed IBM Spectrum Protect Plus versionUse the product's version check mechanism (such as the administrative console, command-line interface, or version information file) to identify the exact version number of IBM Spectrum Protect Plus Container Backup and Restore currently deployed in your environment.Affected if The installed version is 10.1.5 through 10.1.10.x (any version >= 10.1.5 but < 10.1.11)
-
Locate container logs for the affected productAccess the container logs for your IBM Spectrum Protect Plus Container Backup and Restore deployment. These are typically available through your container orchestration platform's log aggregation system, or by accessing the log files directly from the container filesystem.Affected if Container logs exist and are accessible (the vulnerability manifests through log output)
-
Search logs for session token exposureExamine the container logs for patterns resembling session tokens, authentication credentials, or session identifiers. Look for any string that appears to be a token, session ID, or authentication cookie that could be used to impersonate a user.Affected if Any session tokens, authentication tokens, or session identifiers are visible in plain text within the container logs
-
Check for unauthorized access patternsReview access logs and audit trails for any session activity that corresponds to the tokens found in the container logs, particularly from unexpected IP addresses or users.Affected if Session tokens from logs were used to authenticate to the Spectrum Protect Plus server, indicating the vulnerability was exploited
Your environment is affected if you are running any version of IBM Spectrum Protect Plus Container Backup and Restore between 10.1.5 and 10.1.10.x AND you find exposed session tokens in your container logs.
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 · scoped10.1.11
Apply the IBM fix pack (10.1.11 or later) to remediate the session information disclosure. Additionally, restrict access to container logs to trusted personnel only as a defense-in-depth measure.
10.1.11 or later
- Upgrade IBM Spectrum Protect Plus Container Backup and Restore to version 10.1.11 or later
- After upgrading, verify that the role-based access control restrictions are properly enforced
- Review container logs to ensure no session information leakage remains
- Confirm that the fix addresses the improper disclosure of session information that allowed bypass of login security
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spectrum Protect Plus Container Backup And Restore
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22472 — 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-22472 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