dbcve.org
Vbase Web RemoteApplication · Visam

CVE-2021-38417

HIGH · 7.5 CVSS v3.1 Published 2022-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
VISAM VBASE version 11.6.0.6 is vulnerable to improper access control via the web-remote endpoint, which may allow an unauthenticated user viewing access to folders and files in the directory listing.

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 confidence

VISAM VBASE version 11.6.0.6 contains an improper access control vulnerability in its web-remote endpoint. The endpoint fails to enforce authentication requirements, allowing any unauthenticated user to access and view directory listings including folders and files within the system.

MitigationImplement proper authentication and session validation on the web-remote endpoint, and enforce role-based authorization checks before returning any directory listings or file contents to ensure only authenticated, authorized users can access sensitive file system information.

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 Web RemoteApplication
Affected:= 11.6.0.6

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed VBASE version
    Check the installed version of VISAM VBASE or Vbase Web Remote by reviewing the software inventory, program files, or version information in the application (typically found in Help > About or in the installation directory)
    Affected if The installed version is exactly 11.6.0.6
  2. Confirm web-remote component presence
    Verify that the Vbase Web Remote component is installed on the system by checking the installation directory for web-remote related files or services
    Affected if The web-remote component is installed alongside VBASE
  3. Check web-remote service status
    Identify if the web-remote web service is running by reviewing active web services, IIS configurations, or port bindings (commonly ports 8080 or 8443 for VBASE web interfaces)
    Affected if The web-remote HTTP service is actively listening and accessible
  4. Test endpoint accessibility
    Attempt to access the web-remote endpoint URL (typically /vbase/webremote or similar path) from an unauthenticated browser session or using curl without providing credentials
    Affected if Directory listings or file information is returned without requiring login credentials

A user is affected if VBASE version 11.6.0.6 is installed with the web-remote component enabled and the endpoint returns directory listings without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and session validation on the web-remote endpoint, and enforce role-based authorization checks before returning any directory listings or file contents to ensure only authenticated, authorized users can access sensitive file system information.

Recommended fix Moderate confidence

Contact VISAM for the latest fixed version (version higher than 11.6.0.6)

  1. 1. Identify the current VISAM VBASE installation version by checking the application or system information.
  2. 2. Contact VISAM official support or visit their official website to obtain information about the fixed version for CVE-2021-38417.
  3. 3. Download the latest stable version of VISAM VBASE that includes the security fix for improper access control.
  4. 4. Before upgrading, perform a complete backup of the current system configuration and data.
  5. 5. Test the upgrade in a non-production environment to verify functionality.
  6. 6. Apply the upgrade to the production environment following vendor documentation.
  7. 7. Verify that the web-remote endpoint no longer allows unauthenticated access to directory listings.

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

Fix this in Vbase Web Remote Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-38417 — 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-2021-38417 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