dbcve.org
Vbase Automation BaseApplication · Visam

CVE-2022-46286

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-21
Fix available
A fix is available. Upgrade to 11.7.5 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
Versions 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 · high confidence

VISAM 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 cause the application to disclose sensitive information.

MitigationUpdate VISAM VBASE Automation Base to version 11.7.5 or later to remediate this vulnerability.

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
Vbase Automation BaseApplication
Affected:< 11.7.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if VISAM VBASE Automation Base is installed
    Look for VBASE installation directories or check installed programs list on the system. Common locations include C:\Program Files\VISAM or C:\Program Files (x86)\VISAM. On Linux, check /opt/visam or /usr/local/visam.
    Affected if VISAM VBASE Automation Base software is found on the system
  2. Determine the installed version of VBASE
    Locate version information in the installation directory, typically found in an About dialog, version.ini, vbase.exe properties, or documentation shipped with the software. Check the main executable or DLL file properties for version details.
    Affected if Installed version cannot be determined or is older than 11.7.5
  3. Compare installed version against the affected range
    Verify the exact version number found against the vulnerable range: versions prior to 11.7.5. Note that version 11.7.5 itself and later versions are NOT affected.
    Affected if Installed version is lower than 11.7.5 (for example, 11.7.4, 11.6.x, 11.5.x, etc.)
  4. Identify if users have authentication access
    Determine if user accounts are configured and active for the VBASE application, as the vulnerability requires an authenticated user to open the specially crafted file.
    Affected if Authenticated user accounts exist and can access the VBASE application

The system is affected if VISAM VBASE Automation Base is installed with a version lower than 11.7.5 and users have authenticated access to open files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.7.5 or later
Fixed in 11.7.5
Interim mitigation

Update VISAM VBASE Automation Base to version 11.7.5 or later to remediate this vulnerability.

Recommended fix Moderate confidence

VISAM VBASE Automation Base 11.7.5 or later

  1. 1. Identify the current version of VBASE Automation Base installed in the environment
  2. 2. Create a full backup of the VBASE system, including configuration files and project data
  3. 3. Download VISAM VBASE Automation Base version 11.7.5 or later from the official vendor source
  4. 4. Review the vendor's upgrade documentation for version 11.7.5 for any specific prerequisites or procedures
  5. 5. Execute the upgrade following the vendor's recommended upgrade path
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Test that normal operations function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vbase Automation Base Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46286 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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