CVE-2022-41696
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 · uneditedVersions of VISAM VBASE Automation Base prior to 11.7.5 may disclose information if a valid user opens a specially crafted file.
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 confidenceVISAM VBASE Automation Base versions prior to 11.7.5 contain an information disclosure vulnerability where opening a specially crafted file by an authenticated user can reveal sensitive information. The attack requires user interaction (opening the malicious file) and valid credentials.
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< 11.7.5CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Locate VISAM VBASE installationCheck common installation directories for VISAM VBASE Automation Base, such as C:\Program Files\VISAM\ or C:\Program Files (x86)\VISAM\, or search for files named VBASE.exe or similar VBASE components in the system.Affected if VISAM VBASE Automation Base is installed on the system
-
Identify installed versionRight-click the VBASE executable or application file, select Properties, and check the Details tab for version information. Alternatively, look for a version file or readme in the installation directory.Affected if The installed version is lower than 11.7.5
-
Confirm version is in affected rangeCompare the identified version number to the affected range: any version prior to 11.7.5. If the version shows 11.7.5 or later, the system is not affected by this CVE.Affected if Version is 11.7.4 or earlier, or version cannot be determined but product is present
-
Verify authentication is requiredCheck if VBASE user authentication is enabled. This may be configured in the VBASE application settings, user management console, or configuration files within the installation directory.Affected if Authentication is disabled or not required, which would actually change the attack vector context for this specific CVE
The environment is affected if VISAM VBASE Automation Base is installed with a version lower than 11.7.5 and user authentication is active, allowing authenticated users to open files.
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 · scoped11.7.5
Upgrade VISAM VBASE Automation Base to version 11.7.5 or later. Until patched, ensure only trusted files are opened by users and consider network segmentation to limit exposure.
11.7.5
- Upgrade VISAM VBASE Automation Base to version 11.7.5 or later
- Verify the upgrade by confirming the installed version matches the fixed release
- Test that legitimate file operations continue to function properly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41696 — 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-41696 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