Debian Package Tracker

general

source: quagga (main)
version: 1.2.4-3
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]

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

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]

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

lintian reports 10 errors and 3 warnings high

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

Created: 2019-04-07 Last update: 2019-04-07 07:40

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-03-12 00:12

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: 2019-06-26 02:11

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: 2018-04-03 Last update: 2019-06-26 01:58

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: 2019-06-26 00:13

3 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 9c0a6a3f320b82cb8d675c37d1b8e19bb6b188c3
Author: Brett Parker <iDunno@sommitrealweird.co.uk>
Date:   Sat Jan 26 10:33:41 2019 +0000

    Drop build dep on libpcre3-dev

commit 42d8e2105e54d03a24f72323f02a8608dc026962
Author: Ondřej Nový <onovy@debian.org>
Date:   Mon Oct 1 10:14:04 2018 +0200

    d/changelog: Remove trailing whitespaces

commit 6475b0409564e8e092bddf91304f898430b2afc6
Author: Ondřej Nový <onovy@debian.org>
Date:   Mon Oct 1 10:14:01 2018 +0200

    d/copyright: Use https protocol in Format field

Created: 2018-10-01 Last update: 2019-06-25 14:04

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: 2019-06-25 23:31

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-03-12 00:12

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-03-12 00:12

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-03-12 00:12

Standards version of the package is outdated. wishlist

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

Created: 2018-02-16 Last update: 2019-01-27 03:31

testing migrations

This package will soon be part of the auto-readline transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[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)
[2016-10-18] Accepted quagga 1.0.20160315-3 (source amd64 all) into unstable (Florian Weimer)
[2016-10-18] Accepted quagga 0.99.22.4-1+wheezy3+deb7u1 (source amd64 all) into oldstable (Chris Lamb)

bugs [bug history graph]

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

links

homepage
lintian (10, 3)
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-3
9 bugs