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 flutter_rust_bridge_codegen


(25 total, 8 outdated, 3 possibly insecure)

 anyhow^1.0.641.0.75up to date
 atty^ to date
 cargo_metadata^ of date
 cbindgen^ of date
 chrono ⚠️^ insecure
 clap^ to date
 convert_case^ of date
 delegate^ of date
 enum-iterator^ to date
 enum_dispatch^ to date
 fern^ to date
 itertools^ of date
 lazy_static^ to date
 log^ to date
 pathdiff^ to date
 quote^ to date
 regex ⚠️^ insecure
 serde^ to date
 serde_yaml ⚠️^ of date
 strum_macros^ of date
 syn^ to date
 tempfile^ to date
 thiserror^ to date
 toml^ of date
 topological-sort^ to date

Dev dependencies

(1 total, all up-to-date)

 semver^ to date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization


Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

chrono: Potential segfault in `localtime_r` invocations



Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.


No workarounds are known.


regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse


The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.


The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.


We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.


We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.