CVE-2020-35570
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 · uneditedAn issue was discovered in MB connect line mymbCONNECT24, mbCONNECT24 and Helmholz myREX24 and myREX24.virtual through 2.11.2. An unauthenticated attacker is able to access files (that should have been restricted) via forceful browsing.
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 confidenceThe mbCONNECT24 and related products (mymbCONNECT24, myREX24, myREX24.virtual) through version 2.11.2 contain a path traversal or insecure direct object reference vulnerability. An unauthenticated remote attacker can bypass authentication restrictions and access sensitive files on the filesystem by manipulating file paths in HTTP requests (forceful browsing), potentially exposing configuration files, credentials, or other sensitive data.
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<= 2.11.2<= 2.11.2<= 2.11.2<= 2.11.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed version of the productAccess the web interface and look for version information in the about page, footer, help section, or system info page. If CLI access is available, check application logs or version files for the product.Affected if The detected version is 2.11.2 or lower for mbCONNECT24, mymbCONNECT24, Myrex24, or Myrex24.virtual
-
Verify network exposure of the web interfaceReview firewall rules, network ACLs, or reverse proxy configuration to determine if the application's HTTP/HTTPS ports are reachable from untrusted networks or the internet without authentication.Affected if The web interface is directly exposed to untrusted networks without authentication barriers
-
Test for path traversal vulnerability in HTTP requestsUsing a web proxy or curl, send an authenticated or unauthenticated HTTP GET request attempting to access files outside the web root. Common test patterns include manipulating path parameters with ../../ sequences to reach system files.Affected if The application returns file contents from outside the intended web directory, indicating successful path traversal
-
Check for sensitive file exposure via forceful browsingAttempt to access common sensitive endpoints or files such as configuration directories, credential stores, or backup files by directly manipulating URL paths in requests to the application.Affected if Sensitive configuration files, credentials, or application data are returned in the HTTP responses
A system is affected if it runs version 2.11.2 or lower of the listed products AND has its web interface accessible to unauthenticated attackers who can exploit the path traversal to read sensitive 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 dataUpdate to version 2.11.2 or later which contains the vendor patch. If immediate patching is not possible, implement network-level access controls to restrict unauthenticated access to the application's file endpoints.
- Consultation4.0 h
- Implementation3.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35570 — 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-35570 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