CVE-2022-40608
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.6 through 10.1.11 Microsoft File Systems restore operation can download any file on the target machine by manipulating the URL with a directory traversal attack. This results in the restore operation gaining access to files which the operator should not have access to. IBM X-Force ID: 235873.
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 confidenceA directory traversal vulnerability in IBM Spectrum Protect Plus 10.1.6-10.1.11 allows attackers to manipulate URLs in the Microsoft File Systems restore operation to access arbitrary files outside the intended directory, bypassing access controls.
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>= 10.1.6, <= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installationLocate the IBM Spectrum Protect Plus installation directory or check installed programs. Common paths include /opt/ibm/spectrumprotectplus or C:\Program Files\IBM\Spectrum Protect Plus. Verify the product name matches 'IBM Spectrum Protect Plus' or 'Spectrum Protect Plus'.Affected if The product is not installed or the product name does not match IBM Spectrum Protect Plus.
-
Determine installed versionCheck the version of IBM Spectrum Protect Plus. This is typically found in the product GUI under 'Help' > 'About', or via command line using 'dsmc -version' or checking version files in the installation directory. Compare your version against the affected range: 10.1.6 through 10.1.11.Affected if The installed version is 10.1.6, 10.1.7, 10.1.8, 10.1.9, 10.1.10, or 10.1.11.
-
Verify Microsoft File Systems restore is configuredCheck if the Microsoft File Systems backup/restore functionality is enabled. This is typically configured in the IBM Spectrum Protect Plus administrative console under 'Resources' > 'Backup' > 'File Systems' or similar restore job configurations. Look for any Microsoft Windows file system backup or restore job definitions.Affected if Microsoft File Systems restore jobs or configurations exist in the environment.
-
Inspect restore operation URLsIf Microsoft File Systems restore operations are performed, review proxy or web server logs for the restore endpoint. Look for URL patterns that include '..' (dot-dot) sequences or absolute paths like '/etc/' or 'C:\' in the restore request parameters. Check logs for any restore operations with unusual path traversal patterns.Affected if Restore operation requests contain path traversal sequences like '../' or absolute file paths pointing outside the intended restore directory.
You are affected if IBM Spectrum Protect Plus version 10.1.6 through 10.1.11 is installed AND Microsoft File Systems restore functionality is in use, as the directory traversal only applies when this feature is invoked.
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 · scopedUpgrade to a patched version of IBM Spectrum Protect Plus and implement strict input validation on file path parameters in the restore operation.
IBM Spectrum Protect Plus 10.1.12 or later (check IBM Fix Central for specific interim fix)
- 1. Identify the current IBM Spectrum Protect Plus version by accessing the administration console or checking the installed software
- 2. If the current version is between 10.1.6 and 10.1.11 (inclusive), plan for an upgrade
- 3. Review IBM Spectrum Protect Plus release notes and support documentation for the latest available maintenance release
- 4. Download the appropriate fix pack or upgrade package from IBM Fix Central (https://www.ibm.com/support/fixcentral)
- 5. Schedule a maintenance window following standard backup and recovery procedures
- 6. Apply the upgrade following IBM's documented upgrade process for Spectrum Protect Plus
- 7. Verify the upgrade was successful by checking the version number and testing the Microsoft File Systems restore functionality
- 8. Confirm the path traversal vulnerability is resolved by validating that restore operations respect proper access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40608 — 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-40608 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