LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30231: A vulnerability has been identified in SICAM GridEdge (Classic) (All versions < V2.6.6).

A vulnerability has been identified in SICAM GridEdge (Classic) (All versions < V2.6.6). The affected application discloses password hashes of other users upon request. This could allow an authenticated user to retrieve another user's password hash.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

SICAM GridEdge (Classic) before V2.6.6 can expose other users' password hashes to an authenticated user. This is not a remote unauthenticated takeover, but it can weaken account security if hashes are copied and cracked elsewhere.

Executive priority

Treat as a targeted insider or compromised-admin risk. Prioritize remediation for critical grid environments, shared admin teams, or systems reachable from broad operational networks.

Technical view

The issue is an information disclosure flaw, CWE-402, affecting Siemens SICAM GridEdge (Classic) versions below V2.6.6. CVSS 4.0 is 6.9, with network access, low attack complexity, high privileges required, no user interaction, and high confidentiality impact only.

Likely exposure

Exposure is limited to organizations running Siemens SICAM GridEdge (Classic) below V2.6.6, especially where privileged authenticated users can access the application over the network.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. They support only that an authenticated high-privilege user could request another user's password hash.

Researcher notes

Do not assume unauthenticated exploitation. The CVSS vector indicates PR:H and confidentiality-only impact. Focus validation on version identification, authenticated access paths, user-data exposure, and whether password resets are needed after suspected disclosure.

Mitigation direction

  • Inventory SICAM GridEdge (Classic) deployments and identify versions below V2.6.6.
  • Upgrade affected instances to V2.6.6 or later following Siemens guidance.
  • Restrict application access to trusted administrative networks and accounts.
  • Review user accounts and rotate passwords if hash disclosure is suspected.

Validation and detection

  • Confirm each SICAM GridEdge (Classic) instance reports version V2.6.6 or later.
  • Review access logs for unusual authenticated requests involving user data.
  • Verify only authorized privileged users can reach the application interface.
  • Check Siemens advisory SSA-631336 for any environment-specific instructions.
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-402: 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-2022-30231 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
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2022-30231Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiemensSICAM GridEdge (Classic)0unknown
Weakness

CWE details

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

CWE-402 · source CWE mapping

Transmission of Private Resources into a New Sphere ('Resource Leak')

Transmission of Private Resources into a New Sphere ('Resource Leak') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.