LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34995: PiiGAB M-Bus Weak Password Requirements

There are no requirements for setting a complex password for PiiGAB M-Bus, which could contribute to a successful brute force attack if the password is inline with recommended password guidelines.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

PiiGAB M-Bus SoftwarePack 900S may allow weak passwords because it does not require complex password choices. For a business, the risk is unauthorized access through password guessing, especially where the service is reachable over a network. The sources do not cite active exploitation or a confirmed vendor patch.

Executive priority

Treat as a high-priority exposure review for sites using this software. The business urgency comes from network-accessible password guessing risk, not from confirmed active exploitation in the supplied sources.

Technical view

CVE-2023-34995 is classified as CWE-521, weak password requirements. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, scoring 7.5. The impact is confidentiality loss, with no integrity or availability impact recorded in the supplied metadata.

Likely exposure

Exposure is most likely in environments running PiiGAB M-Bus SoftwarePack 900S where authentication is network reachable. The affected metadata is limited and should be verified against local asset inventory and vendor or CISA advisory details.

Exploitation context

The source bundle describes brute-force risk enabled by weak password policy. CISA KEV status is false, and no supplied source states active exploitation. No exploit steps, public exploit evidence, or weaponized details are provided in the bundle.

Researcher notes

The evidence is narrow: weak password requirements, high CVSS confidentiality impact, and one CISA ICS advisory reference. The bundle does not include patch status, detailed attack prerequisites beyond CVSS, or exploit confirmation. Validate product version and advisory details before closing.

Mitigation direction

  • Check PiiGAB and CISA guidance for supported fixes or configuration changes.
  • Inventory PiiGAB M-Bus SoftwarePack 900S deployments and owners.
  • Require strong, unique credentials where the product allows it.
  • Limit network reachability to trusted management paths.
  • Monitor authentication failures and unusual access attempts.

Validation and detection

  • Confirm whether PiiGAB M-Bus SoftwarePack 900S is deployed.
  • Review password policy enforcement for the M-Bus application.
  • Check whether weak passwords are currently accepted.
  • Verify network exposure of the application authentication surface.
  • Review logs for repeated failed authentication attempts.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-521: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-2023-34995 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
2Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-34995Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PiiGABM-Bus SoftwarePack900Sunaffected
Weakness

CWE details

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

CWE-521 · source CWE mapping

Weak Password Requirements

Weak Password Requirements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.