CVE-2022-41320
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 · uneditedVeritas System Recovery (VSR) versions 18 and 21 store a network destination password in the Windows registry during configuration of the backup configuration. This vulnerability could provide a Windows user (who has sufficient privileges) to access a network file system that they were not authorized to access.
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 confidenceVeritas System Recovery versions 18 and 21 store network destination passwords in the Windows registry during backup configuration. A Windows user with sufficient privileges can read these stored credentials from the registry and use them to access network file systems they were not authorized to access.
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>= 18.0, < 18.0.4.57090>= 21, < 21.0.3.62140CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Veritas System Recovery versionOpen Windows Control Panel > Programs and Features, find 'Veritas System Recovery' and note the version column, or run 'veritas.system.recovery.exe -version' from the installation directory if availableAffected if The installed version falls within >= 18.0 and < 18.0.4.57090, or >= 21 and < 21.0.3.62140
-
Confirm network backup destination configurationLaunch Veritas System Recovery, navigate to Backup definition or destination settings, and verify if any network locations (UNC paths or mapped drives) are configured as backup destinationsAffected if Network destinations are configured - the vulnerability only applies when network backup destinations have been set up
-
Inspect registry for stored network credentialsOpen Registry Editor (regedit.exe), browse to the Veritas System Recovery registry keys where backup configuration is stored - look for password or credential fields associated with network destination entries under the product's registry hiveAffected if Plain-text or weakly encrypted passwords are present in the registry for network destination entries - any stored network destination credentials indicate exposure to this vulnerability
-
Verify registry access permissionsRight-click the registry key containing Veritas System Recovery backup settings, select Permissions, and review which user accounts have Read access to the stored credential dataAffected if Non-admin users or unauthorized accounts have Read access to registry keys containing stored network passwords
You are affected if Veritas System Recovery version is 18.0 through 18.0.4.57089 or 21.0 through 21.0.3.62139, AND network backup destinations with stored credentials exist in the registry accessible to your Windows user account.
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 · scoped18.0.4.5709021.0.3.62140
Implement secure credential storage using Windows Credential Manager or equivalent encrypted storage mechanism instead of storing passwords in plain text in the registry. Restrict registry access permissions to limit credential exposure.
Version 18.0.4.57090 or later for 18.x installations; Version 21.0.3.62140 or later for 21.x installations
- Check the current installed version of Veritas System Recovery by opening the application and navigating to Help > About System Recovery
- For version 18.x: Plan to upgrade to version 18.0.4.57090 or later
- For version 21.x: Plan to upgrade to version 21.0.3.62140 or later
- Review the Veritas product compatibility and release notes for the target version before upgrading
- Create a backup of the current System Recovery configuration and any critical data
- Download the fixed version of Veritas System Recovery from the Veritas Support website (www.veritas.com)
- Stop any running backup jobs and the System Recovery service before installation
- Run the installer for the new version and follow the on-screen prompts to complete the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41320 — 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-41320 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