CVE-2025-59177: Generation of Error Message Containing Sensitive Information Vulnerability
Ericsson Packet Core Controller (PCC) versions prior to 1.39 contain a vulnerability in Configuration Management, allowing an attacker to execute specifically crafted commands to reveal system secret through error messages.
Security readout for executives and security teams
Plain-English summary
A highly privileged attacker with adjacent network access could make Ericsson Packet Core Controller reveal a system secret through error messages. The documented impact is loss of confidentiality, not system modification or outage. Exposure is limited to PCC releases earlier than 1.39.
Executive priority
Treat as a moderate, targeted confidentiality risk. Remediate affected telecom control-plane systems promptly, especially where privileged access or management-network segmentation is weak. Escalate if investigation finds secret exposure, because follow-on impact may exceed the CVSS-described disclosure.
Technical view
CVE-2025-59177 is a CWE-209 information-disclosure flaw in PCC Configuration Management. Specifically crafted commands can cause sensitive system information to appear in error messages. CVSS 4.0 is 6.8: adjacent access, low complexity, high privileges, no user interaction, high confidentiality impact, and no stated integrity or availability impact.
Likely exposure
PCC deployments running versions earlier than 1.39 are potentially exposed. The attacker must have adjacent network access and high privileges, substantially limiting reachability. The supplied structured affected record also lists version “0” with default status unaffected, so exact inventory matching should be confirmed against Ericsson’s bulletin.
Exploitation context
The supplied sources do not report active exploitation, and this CVE is not identified as CISA KEV. Successful abuse requires high privileges, adjacent access, and specially crafted commands. Any disclosed secret could nevertheless enable consequential follow-on activity, depending on its purpose and subsequent controls.
Researcher notes
The record supports CWE-209 and a narrow confidentiality impact. It does not identify the secret type, affected component internals, public proof of concept, exploitation, or detailed remediation. The version narrative says earlier than 1.39, while structured affected metadata is ambiguous; validate applicability with Ericsson.
Mitigation direction
Identify PCC deployments and prioritize those running versions earlier than 1.39.
Consult Ericsson’s security bulletin for the supported upgrade or mitigation procedure.
Restrict Configuration Management access to authorized administrators and trusted adjacent networks.
Protect, rotate, or replace exposed secrets if logs or monitoring indicate possible disclosure.
Validation and detection
Confirm each PCC instance’s installed version and Configuration Management exposure.
Verify systems earlier than 1.39 are tracked for vendor-directed remediation.
Review Configuration Management error records for unexpected sensitive-data disclosure.
Audit privileged access and adjacent-network activity for suspicious command execution.
After remediation, confirm error handling no longer exposes system secrets.
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-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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.
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.
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-209 · source CWE mapping
Generation of Error Message Containing Sensitive Information
Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.