This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate kct

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^4.1.84.5.60up to date
 tracing-appender^0.2.20.2.4up to date
 tracing-subscriber ⚠️^0.3.160.3.22maybe insecure

Crate kct_cli

No external dependencies! 🙌

Crate kct_compiler

No external dependencies! 🙌

Crate kct_helper

No external dependencies! 🙌

Crate kct_jsonnet

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 jrsonnet-evaluator^0.4.20.4.2up to date
 jrsonnet-gc^0.4.20.4.2up to date
 jrsonnet-interner^0.4.20.4.2up to date
 jrsonnet-parser^0.4.20.4.2up to date

Crate kct_kube

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 once_cell^1.17.11.21.3up to date
 regex^1.7.11.12.3up to date
 k8s-openapi^0.17.00.27.1out of date
 kube^0.80.03.0.1out of date
 openssl ⚠️^0.10.450.10.75maybe insecure

Crate kct_package

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 globwalk^0.8.00.9.1out of date
 semver^1.0.161.0.27up to date
 url^2.1.12.5.8up to date

Crate kct_testing

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 fs_extra^1.3.01.3.0up to date
 tempfile^3.4.03.26.0up to date

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.