Skip to content
Fencer Vulns
medium 4.3

CVE-2025-43970 json

GoBGP does not properly check the input length

published 2025-04-21 18 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-12350 , GHSA-hqhq-hp5x-xp3w , GO-2025-3630

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

An issue was discovered in GoBGP before 3.35.0. pkg/packet/mrt/mrt.go does not properly check the input length, e.g., by ensuring that there are 12 bytes or 36 bytes (depending on the address family).

Patch / fix

  • go github.com/osrg/gobgp/v3 3.35.0
  • GoBGP GoBGP 3.35.0
  • gobgp Debian 14, Debian 13 3.35.0-1

debian advisories DEBIAN-CVE-2025-43970

  • gobgp Ubuntu Pro 18.04 LTS 1.29-1ubuntu0.1+esm1
  • gobgp Ubuntu Pro 20.04 LTS 2.12.0-1ubuntu0.1~esm2
  • gobgp Ubuntu Pro 22.04 LTS 2.25.0-3ubuntu0.1+esm2
  • gobgp Ubuntu Pro 24.04 LTS 3.23.0-1ubuntu0.3+esm2

ubuntu advisories UBUNTU-CVE-2025-43970

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250422T181640-1.1

opensuse advisories openSUSE-SU-2025:15017-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
GitHub 3.1 4.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/osrg/gobgp
all versions
 no fix listed
go github.com/osrg/gobgp/v3
<3.35.0
3.35.0

Affected products

  • GoBGP GoBGP

Classification

Weakness
  • CWE-1284 Improper Validation of Specified Quantity in Input

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.