Skip to content
Fencer Intel
low 2.9

CVE-2012-1820 json

The bgp_capability_orf function in bgpd in Quagga 0.99.20.1 and earlier allows remote attackers to cause a denial of service (assertion fai…

published 2012-06-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1830

cvss
2.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

The bgp_capability_orf function in bgpd in Quagga 0.99.20.1 and earlier allows remote attackers to cause a denial of service (assertion failure and daemon exit) by leveraging a BGP peering relationship and sending a malformed Outbound Route Filtering (ORF) capability TLV in an OPEN message.

Patch / fix

  • quagga RHEL 6 0.99.15-7.el6_3.2
  • quagga-contrib RHEL 6 0.99.15-7.el6_3.2

red hat advisories RHSA-2012:1259

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-1820 updated cvss 2.9

(bgpd): Assertion failure by processing BGP OPEN message with malformed ORF capability TLV (VU#962587)

  • Red Hat Enterprise Linux Server (v. 6) quagga 0.99.15-7.el6_3.2 Red Hat Enterprise Linux Server Optional (v. 6) quagga 0.99.15-7.el6_3.2, quagga-contrib 0.99.15-7.el6_3.2 Red Hat Enterprise Linux Workstation (v. 6) quagga 0.99.15-7.el6_3.2 Red Hat Enterprise Linux Workstation Optional (v. 6) quagga 0.99.15-7.el6_3.2, quagga-contrib 0.99.15-7.el6_3.2
    fixed: vendor fix RHSA-2012:1259
  • Red Hat Enterprise Linux 5 quagga
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.9 AV:A/AC:M/Au:N/C:N/I:N/A:P

References

Sources

Fencer Intel 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.