LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34574: Password policy evasion in products of MB connect line and Helmholz

In MB connect line mymbCONNECT24, mbCONNECT24 and Helmholz myREX24 and myREX24.virtual in all versions through v2.11.2 an authenticated attacker can change the password of his account into a new password that violates the password policy by intercepting and modifying the request that is send to the server.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Authenticated users could set their own account password to one that violates the configured password policy by modifying the password-change request. This weakens account hygiene but does not show unauthorized access, data theft, or service outage in the supplied sources.

Executive priority

Treat as a hygiene and remote-access control issue, not an emergency breach signal. Address during normal vulnerability remediation, faster where these portals protect operational or industrial access.

Technical view

CVE-2021-34574 affects MB connect line mymbCONNECT24 and mbCONNECT24, plus Helmholz myREX24 and myREX24.virtual, all versions through v2.11.2. The flaw is a password policy evasion issue requiring low-privileged authentication. CVSS 3.1 is 4.3 with low integrity impact only.

Likely exposure

Exposure is limited to organizations running the listed MB connect line or Helmholz remote access products at affected versions through v2.11.2.

Exploitation context

The source bundle does not cite public exploitation or CISA KEV listing. Exploitation requires an authenticated attacker and affects that user account's password compliance, not direct privilege escalation.

Researcher notes

Evidence supports authenticated password policy bypass only. The bundle does not provide exploit details, fixed-release text, or active exploitation evidence. Avoid expanding scope beyond the named products and versions.

Mitigation direction

  • Inventory listed MB connect line and Helmholz products and versions.
  • Check CERT@VDE and vendor guidance for fixed versions or supported remediation.
  • Prioritize upgrades or vendor-directed remediation for versions through v2.11.2.
  • Review accounts for passwords that violate organizational policy.
  • Use compensating account controls where vendor remediation is not immediately available.

Validation and detection

  • Confirm whether affected products are deployed in production or remote access environments.
  • Verify product versions, especially any version through v2.11.2.
  • Review administrative password policy settings and enforcement behavior.
  • Check user accounts for non-compliant passwords after remediation.
  • Retain evidence from vendor advisories and change records.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-669: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-34574 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-34574Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MB connect linemymbCONNECT242Listed
MB connect linembCONNECT242Listed
HelmholzmyREX242Listed
HelmholzmyREX24.virtual2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-669 · source CWE mapping

Incorrect Resource Transfer Between Spheres

Incorrect Resource Transfer Between Spheres represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.