dbcve.org
Debian LinuxOperating system · Debian

CVE-2018-5379

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-19
Fix available
A fix is available. Upgrade to after 1.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Quagga BGP daemon (bgpd) prior to version 1.2.3 can double-free memory when processing certain forms of UPDATE message, containing cluster-list and/or unknown attributes. A successful attack could cause a denial of service or potentially allow an attacker to execute arbitrary code.

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 confidence

Quagga bgpd versions prior to 1.2.3 contain a double-free memory vulnerability when processing BGP UPDATE messages containing cluster-list and/or unknown attributes. This memory corruption can be triggered by specially crafted UPDATE messages from peers, leading to denial of service or potential arbitrary code execution.

MitigationUpgrade Quagga bgpd to version 1.2.3 or later to patch the double-free vulnerability. If immediate upgrade is not possible, restrict BGP peering to trusted sources and monitor for anomalous UPDATE messages.

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
Affected:= 7.0= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.4= 7.6
Enterprise Linux Server EusOperating system
Affected:= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
Affected:= 7.4= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 7.0
QuaggaApplication
Affected:<= 1.2.2

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quagga bgpd installation and version
    Run 'bgpd -v' or 'rpm -q quagga' (RHEL) / 'dpkg -l quagga' (Debian/Ubuntu) to find the installed version. Check if the version is prior to 1.2.3.
    Affected if The installed Quagga bgpd version is 1.2.2 or earlier.
  2. Confirm bgpd service is running
    Run 'ps aux | grep bgpd' or 'systemctl status bgpd' to check if the bgpd daemon is actively running.
    Affected if The bgpd process is running, exposing the vulnerability.
  3. Check for configured BGP peers
    Examine the BGP configuration file (typically /etc/quagga/bgpd.conf or /etc/bgpd.conf) and run 'vtysh -c "show ip bgp summary"' to list configured peers.
    Affected if One or more BGP peers are configured, allowing external parties to send BGP UPDATE messages to the affected system.

You are affected if Quagga bgpd version 1.2.2 or earlier is running with active BGP peers that can send UPDATE messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.2.2
Interim mitigation

Upgrade Quagga bgpd to version 1.2.3 or later to patch the double-free vulnerability. If immediate upgrade is not possible, restrict BGP peering to trusted sources and monitor for anomalous UPDATE messages.

Recommended fix High confidence

Quagga 1.2.3 or later

  1. Update your system's package repository index: 'apt-get update' (Debian/Ubuntu) or 'yum check-update' (RHEL/CentOS)
  2. Identify the installed Quagga packages: 'dpkg -l | grep quagga' or 'rpm -qa | grep quagga'
  3. Upgrade Quagga packages: 'apt-get install --only-upgrade quagga' (Debian/Ubuntu) or 'yum update quagga' (RHEL/CentOS)
  4. Verify the installed version is 1.2.3 or later: 'quagga --version' or check package version
  5. Restart the bgpd service to load the fixed version: 'service bgpd restart' (systemd: 'systemctl restart bgpd')
  6. Verify the BGP daemon is running correctly: 'service bgpd status' or '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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-5379 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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