CVE-2025-59174
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEricsson Packet Core Controller (PCC) versions prior to 1.39 contain a vulnerability where an attacker sending a large volume of specially crafted messages may cause service degradation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEricsson Packet Core Controller (PCC) versions before 1.39 are vulnerable to a denial-of-service condition. An unauthenticated or authenticated attacker can send a large volume of specially crafted messages to trigger resource exhaustion, leading to service degradation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.39CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Packet Core Controller versionAccess the Ericsson Packet Core Controller management interface or use the product's built-in version command. Check system information or about/pages in the admin console. Compare the installed version to the affected range of < 1.39.Affected if The installed version is any version before 1.39 (for example, 1.38.x, 1.37.x, or earlier releases).
-
Determine network exposure of PCC servicesReview network configuration to identify if Ericsson Packet Core Controller services are directly accessible from untrusted networks. Check firewall rules, access control lists, and exposed interfaces.Affected if PCC interfaces are reachable from unauthenticated or untrusted network segments.
-
Inspect for signs of resource exhaustionReview system logs, monitoring dashboards, and performance metrics for indicators of unusual resource consumption, service degradation, or abnormal message volumes being processed.Affected if Logs show sudden spikes in message processing, memory/CPU exhaustion, or service instability without an explanation.
You are affected if your Ericsson Packet Core Controller version is below 1.39 and the service is network-accessible, making it vulnerable to the crafted message-based denial-of-service attack.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.39
Upgrade Ericsson Packet Core Controller to version 1.39 or later. If immediate patching is not possible, implement rate limiting and traffic filtering on upstream network devices to block malicious message patterns.
1.39
- Obtain Packet Core Controller version 1.39 or later from Ericsson's official software distribution channel (support.ericsson.com or designated customer portal)
- Review Ericsson's upgrade documentation for Packet Core Controller
- Execute the upgrade following Ericsson's standard upgrade procedure for PCC
- Verify the upgrade was successful and the service is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59174 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data