CVE-2019-4652
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 through 10.1.4 uses insecure file permissions on restored files and directories in Windows which could allow a local user to obtain sensitive information or perform unauthorized actions. IBM X-Force ID: 170963.
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 versions 10.1.0 through 10.1.4 sets insecure file permissions on restored files and directories in Windows environments, creating overly permissive access controls that allow local users to read sensitive information or perform unauthorized modifications on restored data.
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.0, <= 10.1.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installation and versionCheck the installed version of IBM Spectrum Protect Plus in your environment. This can typically be found in the product's about section, installation directory, or system information. Compare your version against the affected range: 10.1.0 through 10.1.4.Affected if The installed version falls within 10.1.0 to 10.1.4 inclusive.
-
Confirm Windows operating system environmentVerify that the IBM Spectrum Protect Plus server or agent is running on a Windows host. This vulnerability only affects Windows environments.Affected if The product is running on Windows operating systems.
-
Locate restored files and directoriesIdentify any files or directories that have been restored using IBM Spectrum Protect Plus. Check restore job logs, recent restore operations, or known restore destination paths.Affected if Restored files or directories exist in the environment.
-
Examine Windows ACLs on restored objectsUse Windows utilities such as icacls or the Security tab in File Properties to inspect the access control lists (ACLs) on restored files and directories. Look for overly permissive entries such as Everyone, Users, or Authenticated Users having Full Control, Modify, or Read permissions beyond what is intended.Affected if Restored files or directories have ACLs granting excessive permissions to broad groups (such as Everyone having Full Control or Modify access).
Your environment is affected if IBM Spectrum Protect Plus version 10.1.0-10.1.4 is installed on Windows and you have restored files with overly permissive Windows ACLs.
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.
From vendor dataApply the vendor patch for this vulnerability and review/restrict Windows ACLs on restored files to follow least-privilege principles; verify that restored files inherit appropriate security descriptors rather than overly permissive ones.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4652 — 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-2019-4652 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