dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-40318

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to after 8.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue was discovered in bgpd in FRRouting (FRR) through 8.4. By crafting a BGP OPEN message with an option of type 0xff (Extended Length from RFC 9072), attackers may cause a denial of service (assertion failure and daemon restart, or out-of-bounds read). This is possible because of inconsistent boundary checks that do not account for reading 3 bytes (instead of 2) in this 0xff case. NOTE: this behavior occurs in bgp_open_option_parse in the bgp_open.c file, a different location (with a different attack vector) relative to CVE-2022-40302.

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 · high confidence

A buffer boundary check vulnerability exists in bgpd (FRRouting) when parsing BGP OPEN messages containing the RFC 9072 extended length option (type 0xff). The code incorrectly uses 2-byte boundary checks instead of 3-byte checks for this option type, leading to out-of-bounds memory reads or assertion failures that cause daemon restarts.

MitigationUpgrade FRRouting to a patched version beyond 8.4, or apply the vendor patch for CVE-2022-40318 to fix the boundary check in bgp_open_option_parse(). Since BGP is externally exposed, treat this as urgent.

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
Debian LinuxOperating system
Affected:= 10.0= 11.0= 12.0
FrroutingApplication
Affected:<= 8.4

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

CVSS:3.1/AV:N/AC:L/PR:L/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 FRRouting bgpd package is installed
    On Debian systems, run: dpkg -l | grep frr or dpkg -l | grep frrouting
    Affected if The package is installed and the version is unknown or <= 8.4 (check with: dpkg -l frr 2>/dev/null | grep ^ii)
  2. Determine installed FRRouting version
    Run: frr --version or /usr/sbin/bgpd --version to see the exact version number
    Affected if Version is 8.4 or lower, or the version cannot be determined (package may be unpatched)
  3. Check if BGP daemon is enabled
    Run: vtysh -c 'show running-config' | grep 'bgp' or check systemd service status: systemctl is-enabled frr (BGP is typically configured under 'router bgp' in frr.conf)
    Affected if BGP is enabled and configured (vulnerable code path is only reached when bgpd parses incoming BGP OPEN messages)
  4. Verify bgpd process is running
    Run: ps aux | grep bgpd or systemctl status frr (bgpd is the BGP daemon process name)
    Affected if The bgpd daemon is running - this confirms the vulnerable code is active and processing BGP messages

You are affected if FRRouting version is 8.4 or lower AND the bgpd daemon is enabled and running, as the vulnerability triggers when bgpd parses BGP OPEN messages with RFC 9072 extended length options.

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 a release after 8.4
Interim mitigation

Upgrade FRRouting to a patched version beyond 8.4, or apply the vendor patch for CVE-2022-40318 to fix the boundary check in bgp_open_option_parse(). Since BGP is externally exposed, treat this as urgent.

Recommended fix Moderate confidence

FRRouting 8.4.1 or later stable release

  1. Identify the FRRouting package version currently installed (e.g., using 'apt list --installed | grep frr' or 'frr --version')
  2. Update the package repository metadata (e.g., 'apt update')
  3. Upgrade FRRouting to the latest available version (e.g., 'apt install frr' or 'apt install frr=8.4.1*')
  4. Restart the bgpd service to apply the fix (e.g., 'systemctl restart bgpd' or 'service bgpd restart')
  5. Verify the new version is running (e.g., 'bgpd --version')
Caveat Minor: Verify BGP configuration compatibility after upgrade; some deprecated CLI commands may have been removed in newer versions

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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