Skip to content
Noroxi
NVD / CVE Program· CNA certcc

CVE-2018-5378: The Quagga BGP daemon (bgpd) prior to version 1.2.3 does not properly bounds check the data sent with a NOTIFY to a peer, if an attribute…

MediumCVSS 5.9 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 45/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 74.2% (FIRST EPSS); higher than 99.4% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: quagga (openSUSE:Tumbleweed) 1.2.4-2.14; quagga (SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2) 1.1.1-17.7.1; quagga (SUSE:Linux Enterprise Software Development Kit 11 SP4) 0.99.15-0.30.3.1.

Add it to your regular patch cycle. Upgrade to quagga (openSUSE:Tumbleweed) 1.2.4-2.14; quagga (SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2) 1.1.1-17.7.1; quagga (SUSE:Linux Enterprise Software Development Kit 11 SP4) 0.99.15-0.30.3.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The Quagga BGP daemon (bgpd) prior to version 1.2.3 does not properly bounds check the data sent with a NOTIFY to a peer, if an attribute length is invalid. Arbitrary data from the bgpd process may be sent over the network to a peer and/or bgpd may crash.

Published
Feb 19, 2018
Updated
Jun 16, 2026
EPSS
74.2% · 99th percentile

Report tools

JSON

Action score

45

Plan

Add it to your regular patch cycle.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
22 / 30 · 74.2%

CNA vs NVD score

NVD
5.9
CNA · certcc
7.1
1.2 point gap

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-5378

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
quaggaquagga
debiandebian linux
canonicalubuntu linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.

  • Quagga bgpd

    • bpgd and later · before 1.2.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Tumbleweedquaggabefore 1.2.4-2.141.2.4-2.14
SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2quaggabefore 1.1.1-17.7.11.1.1-17.7.1
SUSE:Linux Enterprise Software Development Kit 11 SP4quaggabefore 0.99.15-0.30.3.10.99.15-0.30.3.1
SUSE:Linux Enterprise Software Development Kit 12 SP5quaggabefore 1.1.1-17.13.11.1.1-17.13.1
SUSE:OpenStack Cloud 6quaggabefore 0.99.22.1-16.4.10.99.22.1-16.4.1

Other highest-scoring records for the same primary product.

  • CVE-2018-5379The Quagga BGP daemon (bgpd) prior to version 1.2.3 can double-free memory when processing certain forms of UPDATE message, containing…
    51Plan
  • CVE-2017-16227The aspath_put function in bgpd/bgp_aspath.c in Quagga before 1.2.2 allows remote attackers to cause a denial of service (session drop) via…
    44Plan
  • CVE-2016-1245It was discovered that the zebra daemon in Quagga before 1.0.20161017 suffered from a stack-based buffer overflow when processing IPv6…
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2016-4049May 23, 2016 · The bgp_dump_routes_func function in bgpd/bgp_dump.c in Quagga does not perform size checks when dumping data, which might allow remote…
    31Monitor
  • ← EarlierCVE-2017-5495Jan 24, 2017 · All versions of Quagga, 0.93 through 1.1.0, are vulnerable to an unbounded memory allocation in the telnet 'vty' CLI, leading to a…
    36Monitor
  • Later →CVE-2018-5380Feb 19, 2018 · The Quagga BGP daemon (bgpd) prior to version 1.2.3 can overrun internal BGP code-to-string conversion tables used for debug by 1 pointer…
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:quagga1.2.4-2.14 · openSUSE:TumbleweedPackage registry (OSV)
suse:quagga0.99.22.1-16.4.1 · SUSE:OpenStack Cloud 6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H

nvd-primary

References

All records