CVE-2020-35558
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. There is an SSRF in the in the MySQL access check, allowing an attacker to scan for open ports and gain some information about possible credentials.
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 confidenceAn SSRF (Server-Side Request Forgery) vulnerability exists in the MySQL access check functionality of mbCONNECT24, mymbCONNECT24, and Helmholz myREX24/myREX24.virtual through version 2.11.2. The vulnerable component fails to properly validate URLs or destinations before making outbound requests, allowing attackers to craft requests that force the server to connect to arbitrary internal or external resources.
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
- 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.
-
Identify installed mbCONNECT24 productsCheck for installation of Mbconnect24, mymbCONNECT24, myREX24, or myREX24.virtual by locating installation directories (common paths: C:\Program Files\mbCONNECT24, /opt/mbconnect24, or similar) or running services on the systemAffected if Any of these products are found on the system
-
Check installed product versionLocate the version information in the product's main executable, about dialog, or version file within the installation directory. Compare against the affected range <= 2.11.2Affected if Installed version is 2.11.2 or lower
-
Verify MySQL access check feature is in useExamine the application's configuration files (typically found in the config or settings subdirectory of the installation) for MySQL connection settings or database access configurations that enable the vulnerable MySQL access check functionalityAffected if MySQL access check is configured and enabled in the application settings
-
Review application logs for suspicious outbound requestsInspect application log files (located in logs or similar directory within the installation) for unusual HTTP requests to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) or external destinations that could indicate exploitation of the SSRF vulnerabilityAffected if Logs show outbound requests to unexpected internal IP addresses, localhost, or non-standard ports that were not initiated by legitimate database operations
A system is affected if it runs any of the affected products (Mbconnect24, mymbCONNECT24, myREX24, myREX24.virtual) at version 2.11.2 or lower with the MySQL access check feature enabled.
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 dataUpgrade to version 2.11.2 or later which contains the security fix. As a compensating control, restrict outbound network connections from the application server to only trusted destinations and implement network segmentation to limit exposure of internal services.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35558 — 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-35558 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