CVE-2020-7008
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 · uneditedVISAM VBASE Editor version 11.5.0.2 and VBASE Web-Remote Module may allow input passed in the URL that is not properly verified before use, which may allow an attacker to read arbitrary files from local resources.
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 Editor v11.5.0.2 and VBASE Web-Remote Module fail to properly validate URL input, allowing unauthenticated remote attackers to access local files via directory traversal sequences. This is a path traversal (local file inclusion) vulnerability enabling arbitrary file read.
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.5.0.2all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if VISAM VBASE software is installedInspect system for VBASE installation directories (commonly C:\Program Files\VISAM or similar), or check Windows registry under HKLM\SOFTWARE\VISAM for VBASE entriesAffected if VBASE Editor or VBASE Web-Remote is found on the system
-
Identify VBASE Editor versionLocate the VBASE Editor executable (vbase.exe or similar) and check its file properties for version information, or use command: wmic product where "name like '%VBASE%'" get versionAffected if Version is exactly 11.5.0.2
-
Verify VBASE Web-Remote module presenceCheck for Web-Remote service or IIS extension related to VBASE, look for vbase_webremote.dll or similar web module files in web server directoriesAffected if VBASE Web-Remote module files exist on the system regardless of version
-
Confirm web service is running and accessibleCheck if the VBASE web interface port (typically 8080 or configured port) is listening: run netstat -an | findstr "8080" or check Windows services for VBASE Web service statusAffected if The VBASE web service is running and network-accessible
-
Test for directory traversal vulnerabilitySend a crafted HTTP request with ../ sequences to the VBASE web endpoint, such as GET /..//..//..//windows/win.ini HTTP/1.1, and observe if file content is returnedAffected if The web interface returns file contents when given directory traversal sequences in the URL
A system is affected if VBASE Editor version 11.5.0.2 or any version of VBASE Web-Remote is installed with the web service enabled and accessible, and the URL input accepts directory traversal sequences to read arbitrary 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.
From vendor dataImplement strict input validation restricting URL parameters to allowed paths, reject directory traversal sequences (..), and normalize file paths before access to prevent escape beyond intended directories.
- 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-2020-7008 — 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-2020-7008 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