Debian Package Tracker

general

source: quagga (main)
version: 1.2.4-4
maintainer: Brett Parker (DMD) (DM)
arch: all any
std-ver: 4.1.1
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.99.23.1-1+deb8u5
o-o-sec: 0.99.23.1-1+deb8u5
oldstable: 1.1.1-3+deb9u2
old-sec: 1.1.1-3+deb9u2
stable: 1.2.4-3
testing: 1.2.4-4
unstable: 1.2.4-4

versioned links

0.99.23.1-1+deb8u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.1.1-3+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.4-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.4-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

quagga (13 bugs: 0, 12, 1, 0)
quagga-bgpd (1 bugs: 0, 1, 0, 0)
quagga-core
quagga-doc
quagga-isisd
quagga-ospf6d
quagga-ospfd
quagga-pimd
quagga-ripd
quagga-ripngd

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2019-08-02 Last update: 2020-01-18 03:36

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).

Please fix it.

Created: 2019-07-07 Last update: 2019-11-27 04:00

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).

Please fix it.

Created: 2017-07-28 Last update: 2019-11-27 04:00

lintian reports 10 errors and 4 warnings high

Lintian reports 10 errors and 4 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2019-08-24 Last update: 2019-09-30 01:18

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2019-04-01 Last update: 2020-01-21 21:32

Depends on packages which need a new maintainer normal

The packages that quagga depends on which need a new maintainer are:

dh-exec (#851746)
- Build-Depends: dh-exec

Created: 2019-11-22 Last update: 2020-01-21 18:37

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2018-09-11 Last update: 2020-01-21 15:43

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

quagga-doc could be marked Multi-Arch: foreign

Created: 2016-09-14 Last update: 2020-01-21 21:35

1 ignored security issue in buster low

There is 1 open security issue in buster.

1 issue skipped by the security teams:

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).

Please fix it.

Created: 2018-03-24 Last update: 2019-11-27 04:00

2 ignored security issues in jessie low

There are 2 open security issues in jessie.

2 issues skipped by the security teams:

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).
CVE-2017-5495: 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 Denial-of-Service of Quagga daemons, or even the entire host. When Quagga daemons are configured with their telnet CLI enabled, anyone who can connect to the TCP ports can trigger this vulnerability, prior to authentication. Most distributions restrict the Quagga telnet interface to local access only by default. The Quagga telnet interface 'vty' input buffer grows automatically, without bound, so long as a newline is not entered. This allows an attacker to cause the Quagga daemon to allocate unbounded memory by sending very long strings without a newline. Eventually the daemon is terminated by the system, or the system itself runs out of memory. This is fixed in Quagga 1.1.1 and Free Range Routing (FRR) Protocol Suite 2017-01-10.

Please fix them.

Created: 2017-01-24 Last update: 2019-11-27 04:00

1 ignored security issue in stretch low

There is 1 open security issue in stretch.

1 issue skipped by the security teams:

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).

Please fix it.

Created: 2017-07-28 Last update: 2019-11-27 04:00

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.5.0 instead of 4.1.1).

Created: 2018-02-16 Last update: 2020-01-21 05:05

news

[rss feed]

[2019-08-04] quagga 1.2.4-4 MIGRATED to testing (Debian testing watch)
[2019-08-02] Accepted quagga 1.2.4-4 (source) into unstable (Brett Parker)
[2019-01-29] quagga 1.2.4-3 MIGRATED to testing (Debian testing watch)
[2019-01-26] Accepted quagga 1.2.4-3 (source amd64 all) into unstable (Brett Parker)
[2018-04-13] quagga 1.2.4-2 MIGRATED to testing (Debian testing watch)
[2018-04-02] Accepted quagga 1.2.4-2 (source) into unstable (Brett Parker) (signed by: Steve McIntyre)
[2018-03-24] quagga 1.2.4-1 MIGRATED to testing (Debian testing watch)
[2018-03-18] Accepted quagga 1.2.4-1 (source) into unstable (Brett Parker) (signed by: Steve McIntyre)
[2018-03-18] quagga REMOVED from testing (Debian testing watch)
[2018-02-23] Accepted quagga 0.99.23.1-1+deb8u5 (all source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Salvatore Bonaccorso)
[2018-02-23] Accepted quagga 1.1.1-3+deb9u2 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
[2018-02-16] Accepted quagga 0.99.22.4-1+wheezy3+deb7u3 (source amd64 all) into oldoldstable (Thorsten Alteholz)
[2017-11-18] Accepted quagga 0.99.23.1-1+deb8u4 (all source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Salvatore Bonaccorso)
[2017-11-14] quagga 1.2.2-1 MIGRATED to testing (Debian testing watch)
[2017-11-12] Accepted quagga 1.1.1-3+deb9u1 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
[2017-11-12] Accepted quagga 1.2.2-1 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2017-10-31] Accepted quagga 0.99.22.4-1+wheezy3+deb7u2 (source amd64 all) into oldoldstable (Hugo Lefeuvre)
[2017-04-09] quagga 1.1.1-3 MIGRATED to testing (Debian testing watch)
[2017-04-06] Accepted quagga 1.1.1-3 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2017-04-04] quagga 1.1.1-2 MIGRATED to testing (Debian testing watch)
[2017-03-29] Accepted quagga 1.1.1-2 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2017-02-12] quagga 1.1.1-1 MIGRATED to testing (Debian testing watch)
[2017-01-27] Accepted quagga 1.1.1-1 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2017-01-14] quagga 1.1.0-3 MIGRATED to testing (Debian testing watch)
[2017-01-03] Accepted quagga 1.1.0-3 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2016-12-20] quagga 1.1.0-2 MIGRATED to testing (Debian testing watch)
[2016-12-09] Accepted quagga 1.1.0-2 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
[2016-11-30] Accepted quagga 1.1.0-1 (source amd64 all) into unstable, unstable (Scott Leggett) (signed by: Vincent Bernat)
[2016-10-21] quagga 1.0.20160315-3 MIGRATED to testing (Debian testing watch)
[2016-10-19] Accepted quagga 0.99.23.1-1+deb8u3 (all source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)

bugs [bug history graph]

all: 15
RC: 0
I&N: 14
M&W: 1
F&P: 0
patch: 1

links

homepage
lintian (10, 4)
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
security tracker
screenshots
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.2.4-4build1
9 bugs