dbcve.org
PacketbeatApplication · Elasticsearch

CVE-2025-68382

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 8.19.9 / 9.1.9 or later.
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
Out-of-bounds read (CWE-125) allows an unauthenticated remote attacker to perform a buffer overflow (CAPEC-100) via the NFS protocol dissector, leading to a denial-of-service (DoS) through a reliable process crash when handling truncated XDR-encoded RPC messages.

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

An out-of-bounds read vulnerability exists in the NFS protocol dissector when parsing truncated XDR-encoded RPC messages. An unauthenticated remote attacker can send specially crafted NFS packets that cause the dissector to read beyond buffer boundaries, triggering a buffer overflow and reliable process crash, resulting in denial of service.

MitigationApply the vendor-provided patch for the affected network analysis software. Until then, avoid analyzing untrusted NFS traffic with the affected dissector or disable the NFS protocol dissector.

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
PacketbeatApplication
Affected:>= 7.0.0, <= 7.17.29>= 8.0.0, < 8.19.9>= 9.0.0, < 9.1.9>= 9.2.0, < 9.2.3

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. Verify Packetbeat installation and version
    Run 'packetbeat version' or check the installed package (dpkg -l packetbeat, rpm -qi packetbeat) to obtain the exact version number
    Affected if The installed version falls within any of these ranges: 7.0.0-7.17.29, 8.0.0-8.19.8, 9.0.0-9.1.8, or 9.2.0-9.2.2
  2. Confirm NFS protocol dissector is enabled
    Examine the Packetbeat configuration file (packetbeat.yml) for 'protocols:' section and verify whether 'nfs:' is listed and enabled, or check for 'enabled: true' under the NFS protocol settings
    Affected if The NFS protocol dissector is enabled in the configuration and Packetbeat is parsing NFS traffic
  3. Check if Packetbeat is capturing live NFS traffic
    Review the network interfaces or traffic sources configured in packetbeat.yml under 'packetbeat.interfaces:' or verify if Packetbeat is reading from a capture file containing NFS packets
    Affected if Packetbeat is actively processing or intends to process NFS network traffic from untrusted sources

You are affected if Packetbeat is installed with a version in the affected ranges AND the NFS protocol dissector is enabled AND the system processes NFS traffic from untrusted network sources.

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.

dbcve · scoped
Upgrade available Upgrade to 8.19.9 / 9.1.9 / 9.2.3 or later
Fixed in 8.19.99.1.99.2.3
Interim mitigation

Apply the vendor-provided patch for the affected network analysis software. Until then, avoid analyzing untrusted NFS traffic with the affected dissector or disable the NFS protocol dissector.

Recommended fix High confidence

8.19.9 (or later 8.x), 9.1.9 (or later 9.0.x), 9.2.3 (or later 9.2.x); 7.17.30+ for legacy 7.x or migrate to 8.x/9.x

  1. 1. Identify the current Packetbeat version in use: `packetbeat version`
  2. 2. For Packetbeat 7.x (7.0.0 to 7.17.29): Upgrade to version 7.17.30 or later, or migrate to a supported 8.x/9.x branch
  3. 3. For Packetbeat 8.x (8.0.0 to 8.19.8): Upgrade to version 8.19.9 or later
  4. 4. For Packetbeat 9.0.x (9.0.0 to 9.1.8): Upgrade to version 9.1.9 or later
  5. 5. For Packetbeat 9.2.x (9.2.0 to 9.2.2): Upgrade to version 9.2.3 or later
  6. 6. After upgrade, verify Packetbeat starts successfully and NFS traffic is being processed without crashes
  7. 7. Monitor for any process restarts or errors related to the NFS dissector
Caveat Patch upgrades within the same minor version are generally safe with no breaking changes; verify any custom dissector configurations after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Packetbeat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68382 — 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-2025-68382 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