CVE-2022-45876
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 · high 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 to an attacker.
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.
-
Verify VISAM VBASE installationCheck for the presence of VISAM VBASE Automation Base software on the system using standard software inventory or program listingsAffected if VISAM VBASE is installed on the system
-
Determine installed VBASE versionLocate and read the version information for VISAM VBASE Automation Base, typically found in the application properties, about dialog, or installation directory metadataAffected if The version cannot be determined or is below 11.7.5
-
Compare version to affected rangeCompare the installed version number against the vulnerable range: any version prior to 11.7.5Affected if The installed version is less than 11.7.5
-
Assess user authentication contextDetermine whether user accounts with access to the system have credentials to authenticate to VISAM VBASEAffected if Authenticated users exist who could potentially open files in the application
The environment is affected if VISAM VBASE Automation Base is installed with a version number lower than 11.7.5 and authenticated users can open files within 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
Update VISAM VBASE Automation Base to version 11.7.5 or later. Additionally, enforce user awareness about not opening files from untrusted sources.
VBASE Automation Base version 11.7.5 or later
- Contact VISAM support or visit the official vendor website to obtain version 11.7.5 or later of VBASE Automation Base
- Follow the vendor's standard upgrade procedure for VBASE Automation Base
- After upgrading, verify the application runs correctly and test that the XXE vulnerability is resolved
- Ensure only trusted files are opened in the application as a general security practice
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45876 — 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-45876 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