CVE-2018-5381
No exploitation reported by the sources we read.
- Published2018-02-19
- WeaknessCWE-228 · CWE-835
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The Quagga BGP daemon (bgpd) prior to version 1.2.3 has a bug in its parsing of "Capabilities" in BGP OPEN messages, in the bgp_packet.c:bgp_capability_msg_parse function. The parser can enter an infinite loop on invalid capabilities if a Multi-Protocol capability does not have a recognized AFI/SAFI, causing a denial of service.
Timeline
dates in UTC- 2018-02-1913:29CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-5381?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-5381?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 17.10 | = 17.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0 | no fix published | NVD |
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.2 | ≤ 1.2.2 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
ICSA-19-099-05 Siemens RUGGEDCOM ROX II
RUGGEDCOM ROX II
Fix
- Vendor fix CISA ICSA-19-099-05 · 1 productUpdate to V2.13.0 - Download: The firmware updates for the RUGGEDCOM ROX-based devices can be obtained by contacting the RUGGEDCOM support team at: https://support.industry.siemens.com/my/WW/en/requests#createRequest
- Mitigation from the vendor CISA ICSA-19-099-05 · 1 productSiemens has identified the following specific workarounds and mitigations thatcustomers can apply to reduce the risk: Disable the BGP routing service if not in use in your setup.
- Mitigation from the vendor CISA ICSA-19-099-05 · 1 productSiemens has identified the following specific workarounds and mitigations thatcustomers can apply to reduce the risk: Configure BGP passwords to authenticate BGP neighbours.
Advisories and patches
- cert-portal.siemens.comMitigation
- gogs.quagga.netVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2018-02-19
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-5381?
Is CVE-2018-5381 actively exploited?
What is the CVSS score for CVE-2018-5381?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.