Debian LinuxOperating system · Debian
CVE-2022-40302
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 · uneditedAn 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.
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 confidenceIn FRRouting bgpd through 8.4, parsing BGP OPEN messages with option type 0xff (Extended Length per RFC 9072) reads 3 bytes for length instead of the standard 2 bytes, but boundary checks were not updated accordingly. This causes either assertion failures triggering daemon restarts or out-of-bounds memory reads, leading to denial of service.
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
= 10.0= 11.0= 12.0<= 8.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FRRouting versionRun 'frr --version' or 'bgpd --version' to determine the installed FRRouting versionAffected if version is 8.4 or lower
-
Verify bgpd daemon is runningRun 'ps aux | grep bgpd' or check systemctl status bgpd to confirm the BGP daemon is activeAffected if bgpd daemon is running and version is <= 8.4
-
Confirm BGP is enabledCheck BGP configuration with 'vtysh -c "show running-config" | grep -i bgp' or review /etc/frr/bgpd.confAffected if BGP protocol is configured and active with the vulnerable bgpd version
-
Check for BGP peer configurationsRun 'vtysh -c "show ip bgp neighbors"' to list configured BGP peersAffected if BGP peers are configured and the bgpd version is <= 8.4
A system is affected if it runs FRRouting bgpd version 8.4 or lower with BGP protocol actively configured and peer connections enabled.
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 · scopedUpgrade FRRouting to version 8.4.1 or later which contains the corrected boundary checks. If immediate upgrade is not feasible, restrict BGP peer connections to trusted sources at the network perimeter to reduce attack surface.
FRRouting 8.4.1 or later (or latest available in Debian repositories)
- 1. Identify the FRRouting version currently installed: `frr --version` or `bgpd --version`
- 2. For Debian 10/11/12: Update package lists with `apt update`
- 3. Upgrade FRRouting package: `apt install frr` or `apt install frr=VERSION`
- 4. Restart the bgpd daemon: `systemctl restart bgpd` or `service bgpd restart`
- 5. Verify the fix by checking the new version and confirming bgpd is running: `systemctl status bgpd`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40302 — 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-2022-40302 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