CVE-2025-43973
First published: Mon Apr 21 2025(Updated: )
An issue was discovered in GoBGP before 3.35.0. pkg/packet/rtr/rtr.go does not verify that the input length corresponds to a situation in which all bytes are available for an RTR message.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GoBGP | <3.35.0 | |
| go/github.com/osrg/gobgp/v3 | <3.35.0 | 3.35.0 |
| go/github.com/osrg/gobgp | <3.35.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-43973?
CVE-2025-43973 is classified as a moderate severity vulnerability due to the potential for malformed RTR messages.
How do I fix CVE-2025-43973?
To fix CVE-2025-43973, upgrade GoBGP to version 3.35.0 or later, where the input length verification issue has been addressed.
What is the main issue described in CVE-2025-43973?
The main issue in CVE-2025-43973 is that GoBGP does not verify whether the input length matches the availability of all bytes for an RTR message.
Which versions of GoBGP are affected by CVE-2025-43973?
CVE-2025-43973 affects all versions of GoBGP prior to 3.35.0.
Is CVE-2025-43973 a local or remote vulnerability?
CVE-2025-43973 is considered a remote vulnerability as it can be exploited through BGP routing messages.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/author
- agent/weakness
- agent/severity
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/epss
- agent/tags
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-c5jg-wr5v-2wp2
- alias/CVE-2025-43973
- collector/nvd-cve
- vendor/gobgp
- canonical/gobgp
- package-manager/go