Debian Package Tracker
Register | Log in
Subscribe

kronosnet

Choose email to subscribe with

general
  • source: kronosnet (main)
  • version: 1.33-1
  • maintainer: Debian HA Maintainers (archive) (DMD)
  • uploaders: Ferenc Wágner [DMD]
  • arch: all
  • 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]
  • o-o-stable: 1.20-4
  • oldstable: 1.25-1
  • stable: 1.31-1
  • testing: 1.33-1
  • unstable: 1.33-1
versioned links
  • 1.20-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.25-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.31-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.33-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libknet-dev
  • libknet-doc
  • libknet1t64
  • libnozzle-dev
  • libnozzle1t64
action needed
Debci reports failed tests high
  • unstable: pass (log)
    The tests ran in 0:05:56
    Last run: 2026-05-24T20:46:48.000Z
    Previous status: unknown

  • testing: fail (log)
    The tests ran in 0:02:03
    Last run: 2026-07-22T23:58:09.000Z
    Previous status: unknown

  • stable: pass (log)
    The tests ran in 0:05:43
    Last run: 2026-07-18T00:28:02.000Z
    Previous status: unknown

Created: 2026-07-19 Last update: 2026-07-26 07:30
A new upstream version is available: 1.35 high
A new upstream version 1.35 is available, you should consider packaging it.
Created: 2026-07-03 Last update: 2026-07-26 02:32
3 security issues in trixie high

There are 3 open security issues in trixie.

3 important issues:
  • CVE-2026-15811: A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
  • CVE-2026-15812: A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34). When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets. A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
  • CVE-2026-15813: A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.
Created: 2026-07-25 Last update: 2026-07-25 01:03
3 security issues in sid high

There are 3 open security issues in sid.

3 important issues:
  • CVE-2026-15811: A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
  • CVE-2026-15812: A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34). When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets. A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
  • CVE-2026-15813: A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.
Created: 2026-07-25 Last update: 2026-07-25 01:03
3 security issues in forky high

There are 3 open security issues in forky.

3 important issues:
  • CVE-2026-15811: A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
  • CVE-2026-15812: A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34). When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets. A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
  • CVE-2026-15813: A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.
Created: 2026-07-25 Last update: 2026-07-25 01:03
3 security issues in bullseye high

There are 3 open security issues in bullseye.

3 important issues:
  • CVE-2026-15811: A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
  • CVE-2026-15812: A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34). When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets. A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
  • CVE-2026-15813: A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.
Created: 2026-07-25 Last update: 2026-07-25 01:03
3 security issues in bookworm high

There are 3 open security issues in bookworm.

3 important issues:
  • CVE-2026-15811: A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.
  • CVE-2026-15812: A vulnerability was found in the internal Access Control List (ACL) subsystem of kronosnet (Version affected: <= 1.34). When the framework is explicitly configured to manage dynamic links (accepting network traffic from any IP address) without network payload encryption, the validation architecture implicitly trusts the link ID provided within incoming data packets. A remote, unauthenticated attacker can exploit this lack of validation by spoofing a legitimate link ID inside crafted network frames. This allows the attacker to fully bypass the ACL framework and inject arbitrary data packets into the application layer, potentially leading to data corruption or service instabilities.
  • CVE-2026-15813: A vulnerability was found in the network packet de-fragmentation engine of kronosnet (Version affected <= 1.34). The internal reassembly code does not properly validate sequence numbers of incoming payload fragments. An attacker can exploit this lack of verification by transmitting malformed packets with corrupted sequence parameters. Under specific conditions, this forces the packet processing layer to parse data outside the designated bounds of the internal memory structures, causing an out-of-bounds memory access or heap corruption. This behavior can result in sudden application crashes or system instability.
Created: 2026-07-25 Last update: 2026-07-25 01:03
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-03-31 15:01
testing migrations
  • 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.
news
[rss feed]
  • [2026-02-04] kronosnet 1.33-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-01] Accepted kronosnet 1.33-1 (source) into unstable (Ferenc Wágner)
  • [2025-10-07] kronosnet 1.32-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-05] Accepted kronosnet 1.32-1 (source) into unstable (Ferenc Wágner)
  • [2025-05-06] kronosnet 1.31-1 MIGRATED to testing (Debian testing watch)
  • [2025-04-26] Accepted kronosnet 1.31-1 (source) into unstable (Ferenc Wágner)
  • [2025-01-09] kronosnet 1.30-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-04] Accepted kronosnet 1.30-1 (source) into unstable (Ferenc Wágner)
  • [2024-07-11] kronosnet 1.29-1 MIGRATED to testing (Debian testing watch)
  • [2024-07-08] Accepted kronosnet 1.29-1 (source) into unstable (Ferenc Wágner)
  • [2024-05-03] kronosnet 1.28-2 MIGRATED to testing (Debian testing watch)
  • [2024-03-04] Accepted kronosnet 1.28-2 (source) into unstable (Ferenc Wágner)
  • [2024-02-28] Accepted kronosnet 1.28-1.1 (source) into unstable (Lukas Märdian)
  • [2024-02-01] Accepted kronosnet 1.28-1.1~exp1 (source) into experimental (Graham Inggs)
  • [2023-10-02] kronosnet 1.28-1 MIGRATED to testing (Debian testing watch)
  • [2023-09-29] Accepted kronosnet 1.28-1 (source) into unstable (Ferenc Wágner)
  • [2023-08-04] kronosnet 1.26-1 MIGRATED to testing (Debian testing watch)
  • [2023-08-01] Accepted kronosnet 1.26-1 (source) into unstable (Ferenc Wágner)
  • [2023-01-11] kronosnet 1.25-1 MIGRATED to testing (Debian testing watch)
  • [2023-01-04] Accepted kronosnet 1.25-1 (source) into unstable (Ferenc Wágner)
  • [2022-06-11] kronosnet 1.24-1 MIGRATED to testing (Debian testing watch)
  • [2022-06-01] Accepted kronosnet 1.24-1 (source) into unstable (Ferenc Wágner)
  • [2021-12-03] kronosnet 1.23-2 MIGRATED to testing (Debian testing watch)
  • [2021-11-30] Accepted kronosnet 1.23-2 (source) into unstable (Ferenc Wágner)
  • [2021-11-24] kronosnet 1.23-1 MIGRATED to testing (Debian testing watch)
  • [2021-11-24] kronosnet 1.23-1 MIGRATED to testing (Debian testing watch)
  • [2021-11-21] Accepted kronosnet 1.23-1 (source) into unstable (Ferenc Wágner)
  • [2021-09-02] kronosnet 1.22-1 MIGRATED to testing (Debian testing watch)
  • [2021-08-31] Accepted kronosnet 1.22-1 (source) into unstable (Ferenc Wágner)
  • [2021-08-29] Accepted kronosnet 1.21-2 (source) into unstable (Ferenc Wágner)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1.33-1ubuntu1
  • patches for 1.33-1ubuntu1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing