fastnetmon - Debian Package Tracker

general

source: fastnetmon (main)
version: 1.2.9-1
maintainer: Patrick Matthäi (DMD)
arch: any
std-ver: 4.7.3
VCS: Git (Browse, QA)

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

[pool directory]

oldstable: 1.2.4-2+deb12u1
old-sec: 1.2.4-2+deb12u1
old-bpo: 1.2.8-1~bpo12+1
stable: 1.2.8-1
stable-sec: 1.2.9-0+deb13u1
stable-p-u: 1.2.9-0+deb13u1
testing: 1.2.9-1
unstable: 1.2.9-1

versioned links

1.2.4-2+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.7-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.8-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.8-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.9-0+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.2.9-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

fastnetmon

action needed

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2026-48682: FastNetMon Community Edition through 1.2.9 contains an out-of-bounds read in the IPv4 packet parser. In src/simple_packet_parser_ng.cpp, after validating that the packet contains at least sizeof(ipv4_header_t) bytes (20 bytes), the code advances the local_pointer by '4 * ipv4_header->get_ihl()' (line 164) without validating that (a) IHL >= 5 (the minimum valid value per RFC 791), or (b) 4 * IHL bytes are actually available in the packet. The IHL field is 4 bits, allowing values 0-15, so the advance can be 0-60 bytes. An IHL value of 15 with only 20 bytes validated causes a 40-byte over-read. An IHL of 0-4 causes the pointer to not advance past the IP header, resulting in the TCP/UDP header being parsed from IP header data (type confusion). This vulnerability is reachable via any packet capture interface.
CVE-2026-48697: FastNetMon Community Edition through 1.2.9 does not verify TLS certificates on outbound HTTPS connections. The execute_web_request_secure() function in src/fast_library.cpp creates a boost::asio::ssl::context with tls_client mode and calls set_default_verify_paths() to load CA certificates, but never calls set_verify_mode(boost::asio::ssl::verify_peer). Without this call, OpenSSL performs the TLS handshake without validating the server's certificate chain, making all HTTPS connections vulnerable to man-in-the-middle attacks. This function is used for telemetry reporting to community-stats.fastnetmon.com, which sends system information including CPU model, kernel version, traffic statistics, and software configuration. An attacker can intercept and modify this data or redirect it to a malicious server.

Created: 2026-05-27 Last update: 2026-07-06 14:32

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-48682: FastNetMon Community Edition through 1.2.9 contains an out-of-bounds read in the IPv4 packet parser. In src/simple_packet_parser_ng.cpp, after validating that the packet contains at least sizeof(ipv4_header_t) bytes (20 bytes), the code advances the local_pointer by '4 * ipv4_header->get_ihl()' (line 164) without validating that (a) IHL >= 5 (the minimum valid value per RFC 791), or (b) 4 * IHL bytes are actually available in the packet. The IHL field is 4 bits, allowing values 0-15, so the advance can be 0-60 bytes. An IHL value of 15 with only 20 bytes validated causes a 40-byte over-read. An IHL of 0-4 causes the pointer to not advance past the IP header, resulting in the TCP/UDP header being parsed from IP header data (type confusion). This vulnerability is reachable via any packet capture interface.
CVE-2026-48697: FastNetMon Community Edition through 1.2.9 does not verify TLS certificates on outbound HTTPS connections. The execute_web_request_secure() function in src/fast_library.cpp creates a boost::asio::ssl::context with tls_client mode and calls set_default_verify_paths() to load CA certificates, but never calls set_verify_mode(boost::asio::ssl::verify_peer). Without this call, OpenSSL performs the TLS handshake without validating the server's certificate chain, making all HTTPS connections vulnerable to man-in-the-middle attacks. This function is used for telemetry reporting to community-stats.fastnetmon.com, which sends system information including CPU model, kernel version, traffic statistics, and software configuration. An attacker can intercept and modify this data or redirect it to a malicious server.

Created: 2026-05-27 Last update: 2026-07-06 14:32

4 security issues in bookworm high

There are 4 open security issues in bookworm.

3 important issues:

CVE-2026-48682: FastNetMon Community Edition through 1.2.9 contains an out-of-bounds read in the IPv4 packet parser. In src/simple_packet_parser_ng.cpp, after validating that the packet contains at least sizeof(ipv4_header_t) bytes (20 bytes), the code advances the local_pointer by '4 * ipv4_header->get_ihl()' (line 164) without validating that (a) IHL >= 5 (the minimum valid value per RFC 791), or (b) 4 * IHL bytes are actually available in the packet. The IHL field is 4 bits, allowing values 0-15, so the advance can be 0-60 bytes. An IHL value of 15 with only 20 bytes validated causes a 40-byte over-read. An IHL of 0-4 causes the pointer to not advance past the IP header, resulting in the TCP/UDP header being parsed from IP header data (type confusion). This vulnerability is reachable via any packet capture interface.
CVE-2026-48688: FastNetMon Community Edition through 1.2.9 contains multiple out-of-bounds reads in the BGP MP_REACH_NLRI IPv6 attribute decoder. The function decode_mp_reach_ipv6() in src/bgp_protocol.cpp contains a TODO comment at line 156 explicitly acknowledging 'we should add sanity checks to avoid reads after attribute memory block.' The function casts raw pointers to structure types without verifying sufficient data exists (line 158), uses the attacker-controlled length_of_next_hop field to determine memcpy size (line 181), and computes prefix_length by dereferencing a pointer calculated from multiple attacker-controlled offsets without bounds validation (line 189). The prefix_length is then used to calculate number_of_bytes_required_for_prefix which becomes a memcpy length (line 202) with no check against remaining buffer size.
CVE-2026-48689: FastNetMon Community Edition through 1.2.9 contains an off-by-one heap-based buffer overflow in the dynamic_binary_buffer_t class (src/dynamic_binary_buffer.hpp). Five methods (append_dynamic_buffer, append_data_as_pointer, append_data_as_object_ptr, memcpy_from_ptr, memcpy_from_object_ptr) use an incorrect bounds check of the form 'if (offset + length > maximum_internal_storage_size + 1)' instead of the correct 'if (offset + length > maximum_internal_storage_size)'. This allows writing exactly one byte past the end of the heap-allocated buffer. The class is used pervasively in BGP message encoding/decoding, NetFlow template processing, and Flow Spec NLRI construction. An attacker who can send network traffic (NetFlow, sFlow, IPFIX, or BGP) to a FastNetMon instance can trigger this overflow, potentially achieving arbitrary code execution by corrupting heap metadata. Notably, the append_byte() method uses the correct bounds check, confirming the inconsistency.

1 issue left for the package maintainer to handle:

CVE-2026-48697: (needs triaging) FastNetMon Community Edition through 1.2.9 does not verify TLS certificates on outbound HTTPS connections. The execute_web_request_secure() function in src/fast_library.cpp creates a boost::asio::ssl::context with tls_client mode and calls set_default_verify_paths() to load CA certificates, but never calls set_verify_mode(boost::asio::ssl::verify_peer). Without this call, OpenSSL performs the TLS handshake without validating the server's certificate chain, making all HTTPS connections vulnerable to man-in-the-middle attacks. This function is used for telemetry reporting to community-stats.fastnetmon.com, which sends system information including CPU model, kernel version, traffic statistics, and software configuration. An attacker can intercept and modify this data or redirect it to a malicious server.

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

Created: 2026-05-27 Last update: 2026-07-06 14:32

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 1.2.9-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 4444dbb9ae80d2a510b8a444f4ca37267e32160e
Author: Patrick Matthäi <pmatthaei@debian.org>
Date:   Wed Jul 8 11:04:30 2026 +0200

    * Merge 1.2.9-0+deb13u1 changelog.

Created: 2026-07-08 Last update: 2026-07-08 11:00

1 open merge request in Salsa normal

There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2026-06-16 Last update: 2026-06-16 23:00

2 low-priority security issues in trixie low

There are 2 open security issues in trixie.

2 issues left for the package maintainer to handle:

CVE-2026-48682: (needs triaging) FastNetMon Community Edition through 1.2.9 contains an out-of-bounds read in the IPv4 packet parser. In src/simple_packet_parser_ng.cpp, after validating that the packet contains at least sizeof(ipv4_header_t) bytes (20 bytes), the code advances the local_pointer by '4 * ipv4_header->get_ihl()' (line 164) without validating that (a) IHL >= 5 (the minimum valid value per RFC 791), or (b) 4 * IHL bytes are actually available in the packet. The IHL field is 4 bits, allowing values 0-15, so the advance can be 0-60 bytes. An IHL value of 15 with only 20 bytes validated causes a 40-byte over-read. An IHL of 0-4 causes the pointer to not advance past the IP header, resulting in the TCP/UDP header being parsed from IP header data (type confusion). This vulnerability is reachable via any packet capture interface.
CVE-2026-48697: (needs triaging) FastNetMon Community Edition through 1.2.9 does not verify TLS certificates on outbound HTTPS connections. The execute_web_request_secure() function in src/fast_library.cpp creates a boost::asio::ssl::context with tls_client mode and calls set_default_verify_paths() to load CA certificates, but never calls set_verify_mode(boost::asio::ssl::verify_peer). Without this call, OpenSSL performs the TLS handshake without validating the server's certificate chain, making all HTTPS connections vulnerable to man-in-the-middle attacks. This function is used for telemetry reporting to community-stats.fastnetmon.com, which sends system information including CPU model, kernel version, traffic statistics, and software configuration. An attacker can intercept and modify this data or redirect it to a malicious server.

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

Created: 2026-05-27 Last update: 2026-07-06 14:32

Standards version of the package is outdated. wishlist

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

Created: 2026-03-31 Last update: 2026-06-02 19:31

testing migrations

This package will soon be part of the auto-protobuf 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.
This package will soon be part of the auto-openssl 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.
This package will soon be part of the auto-grpc 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.
This package will soon be part of the auto-abseil 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]

[2026-07-04] Accepted fastnetmon 1.2.9-0+deb13u1 (source amd64) into proposed-updates (Debian FTP Masters) (signed by: Patrick Matthäi)
[2026-07-02] Accepted fastnetmon 1.2.9-0+deb13u1 (source amd64) into stable-security (Debian FTP Masters) (signed by: Patrick Matthäi)
[2026-06-04] fastnetmon 1.2.9-1 MIGRATED to testing (Debian testing watch)
[2026-06-02] Accepted fastnetmon 1.2.9-1 (source) into unstable (Patrick Matthäi)
[2026-02-17] fastnetmon 1.2.8+git20250911-2 MIGRATED to testing (Debian testing watch)
[2026-02-10] Accepted fastnetmon 1.2.8+git20250911-2 (source) into unstable (Patrick Matthäi)
[2025-09-17] fastnetmon 1.2.8+git20250911-1 MIGRATED to testing (Debian testing watch)
[2025-09-11] Accepted fastnetmon 1.2.8+git20250911-1 (source) into unstable (Patrick Matthäi)
[2025-03-06] Accepted fastnetmon 1.2.8-1~bpo12+1 (source) into stable-backports (Patrick Matthäi)
[2024-12-29] Accepted fastnetmon 1.2.4-2+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Patrick Matthäi)
[2024-12-26] Accepted fastnetmon 1.2.4-2+deb12u1 (source) into stable-security (Debian FTP Masters) (signed by: Patrick Matthäi)
[2024-12-25] fastnetmon 1.2.8-1 MIGRATED to testing (Debian testing watch)
[2024-12-23] Accepted fastnetmon 1.2.8-1 (source) into unstable (Patrick Matthäi)
[2024-07-15] Accepted fastnetmon 1.2.7-1~bpo12+1 (source) into stable-backports (Patrick Matthäi)
[2024-07-14] fastnetmon 1.2.7-1 MIGRATED to testing (Debian testing watch)
[2024-07-08] Accepted fastnetmon 1.2.7-1 (source) into unstable (Patrick Matthäi)
[2023-11-06] Accepted fastnetmon 1.2.6-1~bpo12+1 (source) into stable-backports (Patrick Matthäi)
[2023-11-01] Accepted fastnetmon 1.2.5-2~bpo12+1 (source amd64) into stable-backports (Debian FTP Masters) (signed by: Patrick Matthäi)
[2023-11-01] fastnetmon 1.2.6-1 MIGRATED to testing (Debian testing watch)
[2023-10-27] Accepted fastnetmon 1.2.6-1 (source) into unstable (Patrick Matthäi)
[2023-08-28] fastnetmon 1.2.5-2 MIGRATED to testing (Debian testing watch)
[2023-08-23] Accepted fastnetmon 1.2.5-2 (source) into unstable (Patrick Matthäi)
[2023-07-09] fastnetmon 1.2.5-1 MIGRATED to testing (Debian testing watch)
[2023-07-04] Accepted fastnetmon 1.2.5-1 (source) into unstable (Patrick Matthäi)
[2023-04-11] fastnetmon 1.2.4-2 MIGRATED to testing (Debian testing watch)
[2023-03-14] Accepted fastnetmon 1.2.4-2 (source) into unstable (Patrick Matthäi)
[2023-03-09] Accepted fastnetmon 1.2.4-1 (source) into unstable (Patrick Matthäi)
[2023-01-01] fastnetmon 1.2.3-3 MIGRATED to testing (Debian testing watch)
[2022-12-27] Accepted fastnetmon 1.2.3-3 (source) into unstable (Patrick Matthäi)
[2022-11-13] fastnetmon 1.2.3-2 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

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

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.2.9-1build1