CVE-2025-59178: Exposure of Sensitive System Information to an Unauthorized Control Sphere Vulnerability
Ericsson Packet Core Controller (PCC) versions prior to 1.39 contain an Exposure of Sensitive System Information vulnerability in Configuration Management allowing an attacker to enumerate other users on the system.
Security readout for executives and security teams
Plain-English summary
Ericsson Packet Core Controller versions before 1.39 can allow a highly privileged, network-adjacent attacker to enumerate other system users through Configuration Management. This exposes sensitive system information that could support further targeting, but the supplied evidence indicates limited impact and no availability loss.
Executive priority
Schedule remediation through normal vulnerability-management timelines, prioritizing exposed management environments and deployments with broadly assigned privileged access. Escalate if monitoring identifies suspicious enumeration or unauthorized administrative activity. The supplied evidence does not justify emergency, organization-wide disruption.
Technical view
CVE-2025-59178 is a CWE-497 information-exposure flaw in PCC Configuration Management. CVSS 4.0 scores it 4.8: adjacent-network access, low complexity, high privileges, and no user interaction. The vector records low vulnerable-system confidentiality and integrity impacts, with no availability or downstream-system impact.
Likely exposure
Exposure is limited to Ericsson PCC deployments running versions before 1.39. Exploitation requires adjacent-network access and high privileges, reducing broad internet risk. The bundle does not identify particular configurations, interfaces, or deployment patterns that increase exposure.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or public weaponization. An attacker could enumerate other users, potentially improving knowledge of accounts and system structure. No further exploit capability is established.
Researcher notes
The supplied affected-product metadata contains an ambiguous version entry of "0" and a default status of unaffected, while the description explicitly identifies versions before 1.39. Validate exact applicability against Ericsson's bulletin. No affected configuration details, indicators of compromise, or exploitation evidence are supplied.
Mitigation direction
Inventory Ericsson PCC deployments and identify versions earlier than 1.39.
Review Ericsson's security bulletin for the approved remediation and deployment requirements.
Upgrade affected systems to version 1.39 or later following Ericsson guidance.
Restrict Configuration Management access to authorized administrative networks and personnel.
Validation and detection
Confirm each PCC instance reports version 1.39 or later.
Verify Configuration Management is unreachable from untrusted or non-administrative network segments.
Review privileged-account and Configuration Management logs for unexpected user-enumeration activity.
Confirm access controls permit only required administrators and service accounts.
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-497: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-497 · source CWE mapping
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.