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 vrl

Dependencies

(95 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^11.0.0up to date
 ansi_term^0.120.12.1up to date
 arbitrary^11.4.1up to date
 base16^0.20.2.1up to date
 base62^2.2.12.2.1up to date
 base64^0.220.22.1up to date
 bytes^11.10.1up to date
 charset^0.10.1.5up to date
 encoding_rs^0.8.350.8.35up to date
 chrono ⚠️^0.40.4.41maybe insecure
 chrono-tz^0.100.10.3up to date
 ciborium^0.2.20.2.2up to date
 cidr^0.30.3.1up to date
 csv^11.3.1up to date
 codespan-reporting^0.120.12.0up to date
 convert_case^0.7.10.8.0out of date
 crc^3.2.13.3.0up to date
 data-encoding^22.9.0up to date
 digest^0.100.10.7up to date
 dyn-clone^11.0.19up to date
 exitcode^11.1.2up to date
 flate2^1.1.11.1.1up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 iana-time-zone^0.10.1.63up to date
 idna^1.01.0.3up to date
 indexmap^22.9.0up to date
 influxdb-line-protocol^2.0.02.0.0up to date
 indoc^22.0.6up to date
 itertools^0.140.14.0up to date
 lalrpop-util^0.220.22.1up to date
 mlua^0.100.10.3up to date
 nom^78.0.0out of date
 ordered-float^45.0.0out of date
 md-5^0.100.10.6up to date
 parse-size^1.1.01.1.0up to date
 peeking_take_while^11.0.0up to date
 percent-encoding^22.3.1up to date
 pest^22.8.0up to date
 pest_derive^22.8.0up to date
 proptest^11.6.0up to date
 proptest-derive^0.50.5.1up to date
 prettydiff^0.80.8.0up to date
 prettytable-rs^0.100.10.0up to date
 quickcheck^11.0.3up to date
 quoted_printable^0.50.5.1up to date
 psl^22.1.109up to date
 psl-types^22.0.11up to date
 publicsuffix^22.3.0up to date
 rand^0.80.9.1out of date
 regex ⚠️^11.11.1maybe insecure
 roxmltree^0.200.20.0up to date
 rustyline^1515.0.0up to date
 rust_decimal^11.37.1up to date
 seahash^44.1.0up to date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 simdutf8^0.1.50.1.5up to date
 fancy-regex^0.14.00.14.0up to date
 sha-1^0.100.10.1up to date
 sha2^0.100.10.9up to date
 sha3^0.100.10.8up to date
 strip-ansi-escapes^0.20.2.1up to date
 snap^11.1.1up to date
 syslog_loose^0.210.21.0up to date
 termcolor^11.4.1up to date
 thiserror^22.0.12up to date
 tracing^0.10.1.41up to date
 ua-parser^0.20.2.0up to date
 utf8-width^0.10.1.7up to date
 url^22.5.4up to date
 snafu^0.80.8.5up to date
 webbrowser^1.01.0.4up to date
 woothee^0.130.13.0up to date
 community-id^0.20.2.3up to date
 zstd^0.130.13.3up to date
 aes^0.80.8.4up to date
 aes-siv^0.7.00.7.0up to date
 chacha20poly1305^0.100.10.1up to date
 crypto_secretbox^0.10.1.1up to date
 ctr^0.90.9.2up to date
 cbc^0.10.1.2up to date
 cfb-mode^0.80.8.2up to date
 ofb^0.60.6.1up to date
 prost^0.130.13.5up to date
 prost-reflect^0.140.15.2out of date
 unicode-segmentation^1.12.01.12.0up to date
 lz4_flex^0.11.30.11.3up to date
 dns-lookup^22.0.4up to date
 domain^0.10.40.10.4up to date
 hostname^0.40.4.1up to date
 grok^22.0.0up to date
 onig^66.4.0up to date
 tokio^1.441.45.0up to date
 uuid^11.16.0up to date

Dev dependencies

(12 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 criterion^0.50.6.0out of date
 chrono-tz^0.100.10.3up to date
 serde_json^11.0.140up to date
 indoc^22.0.6up to date
 tracing-test^0.20.2.5up to date
 mlua^0.100.10.3up to date
 quickcheck^11.0.3up to date
 regex ⚠️^11.11.1maybe insecure
 paste^11.0.15up to date
 proptest^11.6.0up to date
 proptest-derive^0.50.5.1up to date

Build dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 lalrpop^0.220.22.1up to date
 serde_yaml^0.9.340.9.34+deprecatedup to date
 ua-parser^0.20.2.0up to date

Crate vrl-cli

No external dependencies! 🙌

Crate vrl-tests

Dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 chrono-tz^0.100.10.3up to date
 clap^4.5.374.5.38up to date
 glob^0.30.3.2up to date
 tracing-subscriber^0.3.190.3.19up to date
 tikv-jemallocator^0.6.00.6.0up to date

Crate vrl-fuzz

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 afl^0.15.180.15.18up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

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.

Workarounds

No workarounds are known.

References

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

RUSTSEC-2022-0013

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.

Overview

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.

Mitigations

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.

Acknowledgements

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.