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.
genkit(29 total, 13 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.102 | up to date |
| async-trait | ^0.1 | 0.1.89 | up to date |
| clap | ^4 | 4.6.0 | up to date |
| dashmap | ^5.4 | 6.1.0 | out of date |
| dyn-clone | ^1.0 | 1.0.20 | up to date |
| fastwebsockets | ^0.4 | 0.10.0 | out of date |
| futures | ^0.3 | 0.3.32 | up to date |
| html5ever | ^0.26 | 0.39.0 | out of date |
| hyper ⚠️ | ^0.14 | 1.8.1 | out of date |
| hyper-tls | ^0.5 | 0.6.0 | out of date |
| markup5ever_rcdom | ^0.2 | 0.38.0+unofficial | out of date |
| minijinja | ^1 | 2.18.0 | out of date |
| notify-debouncer-mini | ^0.3 | 0.7.0 | out of date |
| once_cell | ^1 | 1.21.4 | up to date |
| opener | ^0.6 | 0.8.4 | out of date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| promptly | ^0.3 | 0.3.1 | up to date |
| pulldown-cmark | ^0.9 | 0.13.3 | out of date |
| rayon | ^1.6 | 1.11.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.149 | up to date |
| syntect | ^5 | 5.3.0 | up to date |
| time ⚠️ | ^0.3 | 0.3.47 | maybe insecure |
| tokio | ^1.26 | 1.50.0 | up to date |
| toml | ^0.7 | 1.0.7+spec-1.1.0 | out of date |
| tower | ^0.4 | 0.5.3 | out of date |
| tower-http | ^0.4 | 0.6.8 | out of date |
| walkdir | ^2 | 2.5.0 | up to date |
| words-count | ^0.1 | 0.1.6 | up to date |
(3 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.102 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| test-case | ^3 | 3.3.1 | up to date |
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers.
Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.
To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents
but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.
hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data lossWhen decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation,
this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.
To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send
requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible,
any upstream proxies must accept a chunk size greater than 64 bits.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.