CVE-2020-35565
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 and mbCONNECT24 through 2.6.2. The login pages bruteforce detection is disabled by default.
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 confidenceThe mbCONNECT24 and mymbCONNECT24 web interfaces through version 2.6.2 have brute-force detection disabled by default on login pages, allowing attackers to perform unlimited login attempts without rate limiting, account lockout, or CAPTCHA challenges. This enables credential stuffing and brute-force attacks to gain unauthorized access to the platform.
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.6.2<= 2.6.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 mbCONNECT24 or mymbCONNECT24Locate the application version number in the web interface, admin panel, or system documentation. This is typically visible in the About section, help menu, or footer of the web interface.Affected if The installed version is 2.6.2 or lower.
-
Verify the brute-force detection statusAccess the security or authentication settings within the web interface administration panel. Look for a brute-force detection, attack prevention, or login security module. Check whether it is enabled or disabled.Affected if Brute-force detection is disabled or not explicitly enabled in the security settings.
-
Confirm rate limiting is not configured on login pagesExamine the web server or application configuration for rate limiting rules applied to the login endpoint. Check if there are any restrictions on failed login attempts per minute or per hour.Affected if No rate limiting rules are configured or enforced on the login page.
-
Verify account lockout policy is absent or not enforcedReview the user account or authentication settings for an account lockout threshold (such as number of failed attempts before lockout) and lockout duration.Affected if Account lockout is not configured, set to unlimited attempts, or disabled.
A user is affected if their mbCONNECT24 or mymbCONNECT24 installation is version 2.6.2 or lower AND brute-force detection is disabled in the security settings, allowing unlimited login attempts without rate limiting or account lockout protection.
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 dataEnable the built-in brute-force detection mechanism on the login pages, configure appropriate rate limits, account lockout thresholds, and consider implementing CAPTCHA after failed login attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35565 — 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-35565 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