dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-25009

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Ericsson Packet Core Controller (PCC) contains a vulnerability in Access and Mobility Management Function (AMF) where improper input validation can lead to denial of service which may result in 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 confidence

Ericsson Packet Core Controller's Access and Mobility Management Function (AMF) contains improper input validation that can be exploited to cause denial of service, resulting in service degradation. The vulnerability allows attackers to send specially crafted input to trigger the condition.

MitigationApply Ericsson-provided patches for Packet Core Controller; implement additional input validation safeguards at network perimeter as defense-in-depth until vendor fix is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ericsson Packet Core Controller AMF deployment
    Inventory your telecom core network infrastructure to identify if Ericsson Packet Core Controller with the Access and Mobility Management Function (AMF) component is deployed
    Affected if Your environment contains Ericsson Packet Core Controller with AMF module
  2. Assess AMF network accessibility
    Review network diagrams and firewall rules to determine if the AMF service interface is reachable from external or untrusted network segments
    Affected if AMF interface is exposed to network paths accessible by potential attackers outside the trusted core
  3. Locate AMF version information
    Check system documentation, version logs, or package manifests for the installed Ericsson Packet Core Controller AMF version
    Affected if You cannot verify the installed version or the version lags behind vendor releases
  4. Inspect AMF input validation configuration
    Review AMF configuration files and settings related to input validation, message parsing, and request handling
    Affected if Default input validation settings are in use without additional vendor-recommended safeguards

You are affected if Ericsson Packet Core Controller AMF is deployed and the AMF interface is accessible to untrusted network sources, regardless of version verification status

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Ericsson-provided patches for Packet Core Controller; implement additional input validation safeguards at network perimeter as defense-in-depth until vendor fix is available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25009 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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