Summary
This update for cargo-c fixes the following issues:
- CVE-2025-4574: crossbeam-channel: Fixed double-free on drop in Channel::discard_all_messages (bsc#1243179)
- CVE-2025-58160: tracing-subscriber: Fixed log pollution (bsc#1249012)
- CVE-2024-12224: idna: Fixed improper validation of Punycode labels (bsc#1243851)
Other fixes:
- Fixed _service file to have proper versioning
- Update to version 0.10.15~git0.3e178d5:
* Bump actions/download-artifact from 4 to 5
* Update implib requirement from 0.3.5 to 0.4.0
* Add rlib to the targets when building tests
* Allow disabling emission of library version constants in header files
* Bump to cargo 0.90
* Fix static_libraries swallowing sequence of -framework flags
* Fix non-POSIX paths in Libdir under Windows
* Bump actions-rs-plus/clippy-check from 2.2.1 to 2.3.0
* Fix clippy lints
* Bump cargo-0.89, object-0.37.1, cbindgen-0.29
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | cargo-c | 0.10.15-160000.1.1 |
Vulnerabilities 3
-
Medium 6.5
Crossbeam-channel: crossbeam-channel vulnerable to double free on drop
In crossbeam-channel rust crate, the internal `Channel` type's `Drop` method has a race condition which could, in some circumstances, lead to a double-free that could result in memory corruption.
-
Medium 5.1
idna accepts Punycode labels that do not produce any non-ASCII when decoded
Improper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to anoth…
-
Low 2.3
Tracing logging user input may result in poisoning logs with ANSI escape sequences
tracing is a framework for instrumenting Rust programs to collect structured, event-based diagnostic information. Prior to version 0.3.20, tracing-subscriber was vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape…