dbcve.org
FreeBSDOperating system

CVE-2023-3107

HIGH · 7.5 CVSS v3.1 Published 2023-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
A set of carefully crafted ipv6 packets can trigger an integer overflow in the calculation of a fragment reassembled packet's payload length field. This allows an attacker to trigger a kernel panic, resulting in a denial of service.

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

Integer overflow vulnerability in the IPv6 fragment reassembly code path. When processing a crafted sequence of IPv6 fragments, the kernel's calculation of the total reassembled packet's payload length can overflow, resulting in an incorrect length value that triggers a kernel panic and denial of service.

MitigationApply the vendor-supplied kernel patch for CVE-2023-3107. As a defensive measure, consider filtering or rate-limiting fragmented IPv6 traffic at network perimeter until patches are deployed.

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
FreeBSDOperating system
Affected:= 12.4= 13.1= 13.2
Clustered Data OntapApplication
Affected:= 9.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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. Identify operating system and version
    Run `uname -a` on FreeBSD or check system version via NetApp CLI with `version` command
    Affected if The installed version matches FreeBSD 12.4, 13.1, 13.2 or NetApp Clustered Data Ontap 9.0 (or falls within these release branches)
  2. Confirm IPv6 is enabled
    On FreeBSD, run `sysctl net.inet6.ip6.accept_rtadv` or check `/etc/rc.conf` for `ipv6_enable="YES"`. On NetApp, check if IPv6 is configured via CLI
    Affected if IPv6 is enabled and the system processes IPv6 traffic
  3. Verify IPv6 fragment reassembly is active
    On FreeBSD, check `sysctl net.inet6.ip6.frag` tunable values or run `netstat -s -p ip6` to see fragment activity. On NetApp, check if the system handles IPv6 fragments
    Affected if The system is configured to reassemble IPv6 fragments (default behavior)
  4. Compare installed kernel to affected versions
    On FreeBSD, run `freebsd-version -u` to get the base version, or check `/usr/src/sys/conf/NEW_VERSION` if sources are installed. For NetApp, run `system node image` show to see all installed versions
    Affected if The running kernel version matches the unpatched affected versions listed in the CVE

The system is affected if it runs an unpatched FreeBSD 12.4, 13.1, or 13.2 kernel, or NetApp Clustered Data Ontap 9.0, with IPv6 enabled and fragment reassembly processing enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied kernel patch for CVE-2023-3107. As a defensive measure, consider filtering or rate-limiting fragmented IPv6 traffic at network perimeter until patches are deployed.

Recommended fix Moderate confidence

FreeBSD 13.3 or 14.0; NetApp Clustered Data ONTAP 9.x (patched)

  1. Check current FreeBSD version with: uname -a
  2. For FreeBSD 12.4, 13.1, or 13.2: upgrade to a newer stable release (13.3 or 14.0) that contains the fix for CVE-2023-3107
  3. For NetApp Clustered Data ONTAP 9.0: apply the corresponding patch from security.netapp.com (refer to NetApp advisory for specific patch number)
  4. After applying updates, reboot the system to load the patched kernel
  5. Verify the fix is applied by checking system logs for any related kernel updates and confirming system stability with test IPv6 traffic
Caveat Kernel update requires reboot; ensure proper maintenance window and backup before upgrading

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

Fix this in FreeBSD Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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