CVE-2023-46565
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 · uneditedBuffer Overflow vulnerability in osrg gobgp commit 419c50dfac578daa4d11256904d0dc182f1a9b22 allows a remote attacker to cause a denial of service via the handlingError function in pkg/server/fsm.go.
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 confidenceA buffer overflow vulnerability exists in the handlingError function in pkg/server/fsm.go of the osrg GoBGP BGP routing software. A remote attacker can exploit this flaw to cause a denial of service by sending specially crafted BGP messages that trigger the buffer overflow in the finite state machine error handling code.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if GoBGP is installedCheck for the 'gobgp' binary in common locations such as /usr/local/bin/gobgp, /usr/bin/gobgp, or via command: which gobgp. Also check running processes: ps aux | grep gobgpAffected if GoBGP binary or process is found on the system
-
Determine installed GoBGP versionRun 'gobgp --version' or 'gobgp -v' to obtain the version numberAffected if Version is older than the patched version (the vulnerability affects unpatched versions of GoBGP)
-
Check if BGP service is network-exposedVerify if GoBGP is listening on TCP port 179 or other network interfaces. Use 'netstat -tlnp | grep 179' or 'ss -tlnp | grep 179' to check listening portsAffected if GoBGP BGP service is listening on accessible network interfaces, especially untrusted networks
-
Verify BGP peer configurationReview GoBGP configuration files (typically in /etc/gobgp/ or as specified in startup) to list configured BGP peers. Check which peers are allowed: gobgp neighborAffected if BGP peers include untrusted or internet-facing peers that could send crafted messages
-
Check FSM error handling behaviorMonitor GoBGP logs for any errors or crashes related to FSM error handling in pkg/server/fsm.go. Review logs: gobgp log-level or check system logs for gobgp-related entriesAffected if Logs show instability, crashes, or error handling issues in the FSM component
A user is affected if they are running an unpatched version of GoBGP with BGP service exposed to network peers, particularly untrusted ones.
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.
From vendor dataUpdate GoBGP to the patched version that addresses this vulnerability. If a patch is unavailable, consider implementing network-level controls to limit BGP peer connections to trusted sources.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46565 — 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-2023-46565 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