CVE-2022-46300
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 triggered when a valid user opens a specially crafted file. The vulnerability allows the application to disclose sensitive information to the authenticated user through malformed file processing.
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.
-
Identify VBASE Automation Base installationLocate the VISAM VBASE Automation Base installation on the system and determine the installed version number through the application's about dialog, version information in the executable properties, or installation directory metadataAffected if The installed version number is lower than 11.7.5
-
Verify user authentication contextConfirm that the user account accessing VBASE Automation Base is a valid, authenticated user with legitimate access rights to the applicationAffected if The application is accessed by an authenticated user with valid credentials
-
Assess file handling exposureDetermine if the system allows opening external or imported files within VBASE Automation Base, as the vulnerability is triggered through specially crafted file processingAffected if Users can open, import, or load external files into the application
The environment is affected if VISAM VBASE Automation Base is installed at a version prior to 11.7.5 and users with valid authentication can open external files in the application
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. Additionally, enforce user awareness training to avoid opening untrusted or specially crafted files from unverified sources.
11.7.5
- 1. Identify current VBASE Automation Base version by checking the application or system information
- 2. Back up all VBASE Automation Base data, configurations, and project files before upgrading
- 3. Download VBASE Automation Base version 11.7.5 or later from the official VISAM download portal or vendor distribution channel
- 4. Review the VISAM VBASE Automation Base installation/upgrade documentation for version-specific migration requirements
- 5. Execute the installer or upgrade procedure according to vendor documentation
- 6. Verify the upgraded version is 11.7.5 or later and confirm all services start correctly
- 7. Test that normal VBASE Automation Base functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46300 — 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-46300 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