suricata - Debian Package Tracker

general

source: suricata (main)
version: 1:6.0.1-2
maintainer: Pierre Chifflier (DMD)
uploaders: Sascha Steinbiss [DMD] – Arturo Borrero Gonzalez [DMD]
arch: all
std-ver: 4.5.0
VCS: Git (Browse, QA)

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

[pool directory]

oldstable: 3.2.1-1+deb9u1
old-bpo: 1:4.1.2-2~bpo9+1
stable: 1:4.1.2-2+deb10u1
stable-bpo: 1:6.0.1-2~bpo10+1
testing: 1:6.0.1-2
unstable: 1:6.0.1-2
exp: 1:6.0.2-1~exp1

versioned links

3.2.1-1+deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:4.1.2-2~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:4.1.2-2+deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:6.0.1-2~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:6.0.1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:6.0.2-1~exp1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

suricata (3 bugs: 0, 3, 0, 0)
suricata-oinkmaster

action needed

A new upstream version is available: 6.0.2 high

A new upstream version 6.0.2 is available, you should consider packaging it.

Created: 2021-03-05 Last update: 2021-04-12 11:02

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: 2020-12-11 Last update: 2021-04-07 13:35

2 bugs tagged patch in the BTS normal

The BTS contains patches fixing 2 bugs, consider including or untagging them.

Created: 2020-10-19 Last update: 2021-04-12 13:03

Fails to build during reproducibility 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: 2021-03-31 Last update: 2021-04-12 08:37

13 low-priority security issues in buster low

There are 13 open security issues in buster.

13 issues left for the package maintainer to handle:

CVE-2019-10050: (needs triaging) A buffer over-read issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the decode-mpls.c function DecodeMPLS is composed only of a packet of source address and destination address plus the correct type field and the right number for shim, an attacker can manipulate the control flow, such that the condition to leave the loop is true. After leaving the loop, the network packet has a length of 2 bytes. There is no validation of this length. Later on, the code tries to read at an empty position, leading to a crash.
CVE-2019-10051: (needs triaging) An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfcm) => { ft.new_chunk }" item, then the program enters an smb/files.rs error condition and crashes.
CVE-2019-10052: (needs triaging) An issue was discovered in Suricata 4.1.3. If the network packet does not have the right length, the parser tries to access a part of a DHCP packet. At this point, the Rust environment runs into a panic in parse_clientid_option in the dhcp/parser.rs file.
CVE-2019-10053: (needs triaging) An issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the function SSHParseBanner is composed only of a \n character, then the program runs into a heap-based buffer over-read. This occurs because the erroneous search for \r results in an integer underflow.
CVE-2019-10054: (needs triaging) An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for the length of reply.data. It causes an invalid memory access and the program crashes within the nfs/nfs3.rs file.
CVE-2019-10055: (needs triaging) An issue was discovered in Suricata 4.1.3. The function ftp_pasv_response lacks a check for the length of part1 and part2, leading to a crash within the ftp/mod.rs file.
CVE-2019-10056: (needs triaging) An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28 long, in the first iteration it subtracts 14 bytes. Then, it is working with a packet length of 14. At this point, the case distinction says it is a valid packet. After that it casts the packet, but this packet has no type, and the program crashes at the type case distinction.
CVE-2019-1010279: (needs triaging) Open Information Security Foundation Suricata prior to version 4.1.3 is affected by: Denial of Service - TCP/HTTP detection bypass. The impact is: An attacker can evade a signature detection with a specialy formed sequence of network packets. The component is: detect.c (https://github.com/OISF/suricata/pull/3625/commits/d8634daf74c882356659addb65fb142b738a186b). The attack vector is: An attacker can trigger the vulnerability by a specifically crafted network TCP session. The fixed version is: 4.1.3.
CVE-2019-15699: (needs triaging) An issue was discovered in app-layer-ssl.c in Suricata 4.1.4. Upon receiving a corrupted SSLv3 (TLS 1.2) packet, the parser function TLSDecodeHSHelloExtensions tries to access a memory region that is not allocated, because the expected length of HSHelloExtensions does not match the real length of the HSHelloExtensions part of the packet.
CVE-2019-16410: (needs triaging) An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function Defrag4Reassemble in defrag.c tries to access a memory region that is not allocated, because of a lack of header_len checking.
CVE-2019-16411: (needs triaging) An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.
CVE-2019-18625: (needs triaging) An issue was discovered in Suricata 5.0.0. It was possible to bypass/evade any tcp based signature by faking a closed TCP session using an evil server. After the TCP SYN packet, it is possible to inject a RST ACK and a FIN ACK packet with a bad TCP Timestamp option. The client will ignore the RST ACK and the FIN ACK packets because of the bad TCP Timestamp option. Both linux and windows client are ignoring the injected packets.
CVE-2019-18792: (needs triaging) An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake FIN packet is injected just before the PUSH ACK packet we want to bypass. The PUSH ACK packet (containing the data) will be ignored by Suricata because it overlaps the FIN packet (the sequence and ack number are identical in the two packets). The client will ignore the fake FIN packet because the ACK flag is not set. Both linux and windows clients are ignoring the injected packet.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-02-19 Last update: 2021-03-21 19:04

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2020-12-11 Last update: 2020-12-11 20:05

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.1 instead of 4.5.0).

Created: 2020-11-17 Last update: 2020-12-11 19:01

testing migrations

This package will soon be part of the auto-hiredis 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]

[2021-03-23] Accepted suricata 1:6.0.2-1~exp1 (source amd64 all) into experimental (Sascha Steinbiss)
[2021-02-01] Accepted suricata 1:6.0.1-2~bpo10+1 (source amd64 all) into buster-backports (Sascha Steinbiss)
[2020-12-13] suricata 1:6.0.1-2 MIGRATED to testing (Debian testing watch)
[2020-12-11] Accepted suricata 1:6.0.1-2 (source) into unstable (Sascha Steinbiss)
[2020-12-10] Accepted suricata 1:6.0.1-1 (source) into unstable (Sascha Steinbiss)
[2020-12-09] Accepted suricata 1:6.0.1-1~exp2 (source) into experimental (Sascha Steinbiss)
[2020-12-09] Accepted suricata 1:6.0.1-1~exp1 (source) into experimental (Sascha Steinbiss)
[2020-05-10] Accepted suricata 1:4.1.2-2+deb10u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Sascha Steinbiss)
[2020-05-05] Accepted suricata 1:5.0.3-1~bpo10+1 (source amd64 all) into buster-backports, buster-backports (Debian FTP Masters) (signed by: Sascha Steinbiss)
[2020-05-04] suricata 1:5.0.3-1 MIGRATED to testing (Debian testing watch)
[2020-04-29] Accepted suricata 1:5.0.3-1 (source) into unstable (Sascha Steinbiss)
[2020-02-24] suricata 1:5.0.2-3 MIGRATED to testing (Debian testing watch)
[2020-02-22] Accepted suricata 1:5.0.2-3 (source) into unstable (Sascha Steinbiss)
[2020-02-22] Accepted suricata 1:5.0.2-2 (source amd64 all) into unstable (Sascha Steinbiss)
[2020-02-21] Accepted suricata 1:5.0.2-1 (source) into unstable (Sascha Steinbiss)
[2020-01-30] Accepted suricata 2.0.7-2+deb8u5 (source amd64) into oldoldstable (Mike Gabriel)
[2020-01-16] Accepted suricata 1:5.0.1-1~exp1 (source amd64 all) into experimental (Sascha Steinbiss)
[2019-10-31] Accepted suricata 1:5.0.0-1~exp2 (source) into experimental (Sascha Steinbiss)
[2019-10-31] Accepted suricata 1:5.0.0-1~exp1 (source) into experimental (Sascha Steinbiss)
[2019-10-11] suricata 1:4.1.5-2 MIGRATED to testing (Debian testing watch)
[2019-10-09] Accepted suricata 1:4.1.5-2 (source) into unstable (Sascha Steinbiss)
[2019-09-25] Accepted suricata 1:4.1.5-1 (source) into unstable (Sascha Steinbiss)
[2019-09-21] suricata 1:4.1.4-7 MIGRATED to testing (Debian testing watch)
[2019-09-18] Accepted suricata 1:4.1.4-7 (source) into unstable (Sascha Steinbiss)
[2019-09-14] suricata 1:4.1.4-6 MIGRATED to testing (Debian testing watch)
[2019-09-11] Accepted suricata 1:4.1.4-6 (source) into unstable (Sascha Steinbiss)
[2019-08-31] suricata 1:4.1.4-5 MIGRATED to testing (Debian testing watch)
[2019-08-12] Accepted suricata 1:4.1.4-5 (source) into unstable (Sascha Steinbiss)
[2019-07-24] Accepted suricata 1:4.1.4-4 (source) into unstable (Sascha Steinbiss)
[2019-07-22] Accepted suricata 1:4.1.4-3 (source) into unstable (Sascha Steinbiss)

bugs [bug history graph]

all: 5
RC: 0
I&N: 5
M&W: 0
F&P: 0
patch: 2

links

homepage
buildd: logs, exp, checks, clang, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debci