wikimedia/irc/ircservserv: main (log #573593)

sourcepatches

This run took 74 seconds.

$ date
--- stdout ---
Wed Apr 27 14:06:09 UTC 2022

--- end ---
$ git clone file:///srv/git/wikimedia-irc-ircservserv.git repo --depth=1 -b master
--- stderr ---
Cloning into 'repo'...
--- stdout ---

--- end ---
$ git config user.name libraryupgrader
--- stdout ---

--- end ---
$ git config user.email tools.libraryupgrader@tools.wmflabs.org
--- stdout ---

--- end ---
$ git submodule update --init
--- stdout ---

--- end ---
$ grr init
--- stdout ---
Installed commit-msg hook.

--- end ---
$ git show-ref refs/heads/master
--- stdout ---
75f22c1780f26ed08c20c168de1d902dab6320bc refs/heads/master

--- end ---
$ cargo-audit audit --json
--- stdout ---
{"database":{"advisory-count":404,"last-commit":"b2ba503c747d041d02eeef6b9477664aefcc97fb","last-updated":"2022-04-19T00:03:30Z"},"lockfile":{"dependency-count":99},"settings":{"target_arch":null,"target_os":null,"severity":null,"ignore":[],"informational_warnings":["unmaintained"],"package_scope":null},"vulnerabilities":{"found":true,"count":5,"list":[{"advisory":{"id":"RUSTSEC-2020-0159","package":"chrono","title":"Potential segfault in `localtime_r` invocations","description":"### Impact\n\nUnix-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.\n\n### Workarounds\n\nNo workarounds are known.\n\n### References\n\n- [time-rs/time#293](https://github.com/time-rs/time/issues/293)","date":"2020-11-10","aliases":[],"related":["CVE-2020-26235","RUSTSEC-2020-0071"],"collection":"crates","categories":["code-execution","memory-corruption"],"keywords":["segfault"],"cvss":null,"informational":null,"url":"https://github.com/chronotope/chrono/issues/499","references":[],"withdrawn":null},"versions":{"patched":[],"unaffected":[]},"affected":null,"package":{"name":"chrono","version":"0.4.19","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73","dependencies":[{"name":"libc","version":"0.2.94","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"num-integer","version":"0.1.44","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"num-traits","version":"0.2.14","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"time","version":"0.1.43","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"winapi","version":"0.3.9","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null}},{"advisory":{"id":"RUSTSEC-2022-0013","package":"regex","title":"Regexes with large repetitions on empty sub-expressions take a very long time to parse","description":"The Rust Security Response WG was notified that the `regex` crate did not\nproperly limit the complexity of the regular expressions (regex) it parses. An\nattacker could use this security issue to perform a denial of service, by\nsending a specially crafted regex to a service accepting untrusted regexes. No\nknown vulnerability is present when parsing untrusted input with trusted\nregexes.\n\nThis issue has been assigned CVE-2022-24713. The severity of this vulnerability\nis \"high\" when the `regex` crate is used to parse untrusted regexes. Other uses\nof the `regex` crate are not affected by this vulnerability.\n\n## Overview\n\nThe `regex` crate features built-in mitigations to prevent denial of service\nattacks caused by untrusted regexes, or untrusted input matched by trusted\nregexes. Those (tunable) mitigations already provide sane defaults to prevent\nattacks. This guarantee is documented and it's considered part of the crate's\nAPI.\n\nUnfortunately a bug was discovered in the mitigations designed to prevent\nuntrusted regexes to take an arbitrary amount of time during parsing, and it's\npossible to craft regexes that bypass such mitigations. This makes it possible\nto perform denial of service attacks by sending specially crafted regexes to\nservices accepting user-controlled, untrusted regexes.\n\n## Affected versions\n\nAll versions of the `regex` crate before or equal to 1.5.4 are affected by this\nissue. The fix is include starting from  `regex` 1.5.5.\n\n## Mitigations\n\nWe recommend everyone accepting user-controlled regexes to upgrade immediately\nto the latest version of the `regex` crate.\n\nUnfortunately there is no fixed set of problematic regexes, as there are\npractically infinite regexes that could be crafted to exploit this\nvulnerability. Because of this, we do not recommend denying known problematic\nregexes.\n\n## Acknowledgements\n\nWe want to thank Addison Crump for responsibly disclosing this to us according\nto the [Rust security policy][1], and for helping review the fix.\n\nWe also want to thank Andrew Gallant for developing the fix, and Pietro Albini\nfor coordinating the disclosure and writing this advisory.\n\n[1]: https://www.rust-lang.org/policies/security","date":"2022-03-08","aliases":["CVE-2022-24713"],"related":[],"collection":"crates","categories":["denial-of-service"],"keywords":[],"cvss":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","informational":null,"url":"https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw","references":[],"withdrawn":null},"versions":{"patched":[">=1.5.5"],"unaffected":[]},"affected":null,"package":{"name":"regex","version":"1.5.4","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"d07a8629359eb56f1e2fb1652bb04212c072a87ba68546a04065d525673ac461","dependencies":[{"name":"aho-corasick","version":"0.7.18","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"memchr","version":"2.4.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"regex-syntax","version":"0.6.25","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null}},{"advisory":{"id":"RUSTSEC-2020-0071","package":"time","title":"Potential segfault in the time crate","description":"### Impact\n\nUnix-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.\n\nThe affected functions from time 0.2.7 through 0.2.22 are:\n\n- `time::UtcOffset::local_offset_at`\n- `time::UtcOffset::try_local_offset_at`\n- `time::UtcOffset::current_local_offset`\n- `time::UtcOffset::try_current_local_offset`\n- `time::OffsetDateTime::now_local`\n- `time::OffsetDateTime::try_now_local`\n\nThe affected functions in time 0.1 (all versions) are:\n\n- `at`\n- `at_utc`\n- `now`\n\nNon-Unix targets (including Windows and wasm) are unaffected.\n\n### Patches\n\nPending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.\n\nUsers and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.\n\nUsers of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.\n\n### Workarounds\n\nNo workarounds are known.\n\n### References\n\ntime-rs/time#293","date":"2020-11-18","aliases":["CVE-2020-26235"],"related":[],"collection":"crates","categories":["code-execution","memory-corruption"],"keywords":["segfault"],"cvss":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","informational":null,"url":"https://github.com/time-rs/time/issues/293","references":[],"withdrawn":null},"versions":{"patched":[">=0.2.23"],"unaffected":["=0.2.0","=0.2.1","=0.2.2","=0.2.3","=0.2.4","=0.2.5","=0.2.6"]},"affected":{"arch":[],"os":["linux","redox","solaris","android","ios","macos","netbsd","openbsd","freebsd"],"functions":{"time::OffsetDateTime::now_local":["<0.2.23"],"time::OffsetDateTime::try_now_local":["<0.2.23"],"time::UtcOffset::current_local_offset":["<0.2.23"],"time::UtcOffset::local_offset_at":["<0.2.23"],"time::UtcOffset::try_current_local_offset":["<0.2.23"],"time::UtcOffset::try_local_offset_at":["<0.2.23"],"time::at":["^0.1"],"time::at_utc":["^0.1"],"time::now":["^0.1"]}},"package":{"name":"time","version":"0.1.43","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"ca8a50ef2360fbd1eeb0ecd46795a87a19024eb4b53c5dc916ca1fd95fe62438","dependencies":[{"name":"libc","version":"0.2.94","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"winapi","version":"0.3.9","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null}},{"advisory":{"id":"RUSTSEC-2021-0072","package":"tokio","title":"Task dropped in wrong thread when aborting `LocalSet` task","description":"When aborting a task with `JoinHandle::abort`, the future is dropped in the\nthread calling abort if the task is not currently being executed. This is\nincorrect for tasks spawned on a `LocalSet`.\n\nThis can easily result in race conditions as many projects use `Rc` or `RefCell`\nin their Tokio tasks for better performance.\n\nSee [tokio#3929][issue] for more details.\n\n[issue]: https://github.com/tokio-rs/tokio/issues/3929","date":"2021-07-07","aliases":["CVE-2021-38191"],"related":[],"collection":"crates","categories":["memory-corruption"],"keywords":["race condition","send"],"cvss":null,"informational":null,"url":"https://github.com/tokio-rs/tokio/issues/3929","references":[],"withdrawn":null},"versions":{"patched":[">=1.5.1, <1.6.0",">=1.6.3, <1.7.0",">=1.7.2, <1.8.0",">=1.8.1"],"unaffected":["<0.3.0"]},"affected":{"arch":[],"os":[],"functions":{"tokio::task::JoinHandle::abort":["<=1.8.0, >=0.3.0"]}},"package":{"name":"tokio","version":"1.6.0","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"bd3076b5c8cc18138b8f8814895c11eb4de37114a5d127bafdc5e55798ceef37","dependencies":[{"name":"autocfg","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"bytes","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"libc","version":"0.2.94","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"memchr","version":"2.4.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"mio","version":"0.7.11","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"num_cpus","version":"1.13.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"once_cell","version":"1.7.2","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"parking_lot","version":"0.11.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"pin-project-lite","version":"0.2.6","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"signal-hook-registry","version":"1.3.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"tokio-macros","version":"1.2.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"winapi","version":"0.3.9","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null}},{"advisory":{"id":"RUSTSEC-2021-0124","package":"tokio","title":"Data race when sending and receiving after closing a `oneshot` channel","description":"If a `tokio::sync::oneshot` channel is closed (via the\n[`oneshot::Receiver::close`] method), a data race may occur if the\n`oneshot::Sender::send` method is called while the corresponding\n`oneshot::Receiver` is `await`ed or calling `try_recv`.\n\nWhen these methods are called concurrently on a closed channel, the two halves\nof the channel can concurrently access a shared memory location, resulting in a\ndata race. This has been observed to [cause memory corruption][corruption].\n\nNote that the race only occurs when **both** halves of the channel are used\nafter the `Receiver` half has called `close`. Code where `close` is not used, or where the\n`Receiver` is not `await`ed and `try_recv` is not called after calling `close`,\nis not affected.\n\nSee [tokio#4225][issue] for more details.\n\n[corruption]: https://github.com/tokio-rs/tokio/issues/4225#issuecomment-967434847\n[issue]: https://github.com/tokio-rs/tokio/issues/4225\n[`oneshot::Receiver::close`]: https://docs.rs/tokio/1.14.0/tokio/sync/oneshot/struct.Receiver.html#method.close","date":"2021-11-16","aliases":["CVE-2021-45710"],"related":[],"collection":"crates","categories":["memory-corruption","thread-safety"],"keywords":["race condition"],"cvss":null,"informational":null,"url":"https://github.com/tokio-rs/tokio/issues/4225","references":[],"withdrawn":null},"versions":{"patched":[">=1.8.4, <1.9.0",">=1.13.1"],"unaffected":["<0.1.14"]},"affected":{"arch":[],"os":[],"functions":{"tokio::sync::oneshot::Receiver::close":["<=1.13.0, >=0.1.14"]}},"package":{"name":"tokio","version":"1.6.0","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"bd3076b5c8cc18138b8f8814895c11eb4de37114a5d127bafdc5e55798ceef37","dependencies":[{"name":"autocfg","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"bytes","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"libc","version":"0.2.94","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"memchr","version":"2.4.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"mio","version":"0.7.11","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"num_cpus","version":"1.13.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"once_cell","version":"1.7.2","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"parking_lot","version":"0.11.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"pin-project-lite","version":"0.2.6","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"signal-hook-registry","version":"1.3.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"tokio-macros","version":"1.2.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"winapi","version":"0.3.9","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null}}]},"warnings":{"yanked":[{"kind":"yanked","package":{"name":"tokio","version":"1.6.0","source":"registry+https://github.com/rust-lang/crates.io-index","checksum":"bd3076b5c8cc18138b8f8814895c11eb4de37114a5d127bafdc5e55798ceef37","dependencies":[{"name":"autocfg","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"bytes","version":"1.0.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"libc","version":"0.2.94","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"memchr","version":"2.4.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"mio","version":"0.7.11","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"num_cpus","version":"1.13.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"once_cell","version":"1.7.2","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"parking_lot","version":"0.11.1","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"pin-project-lite","version":"0.2.6","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"signal-hook-registry","version":"1.3.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"tokio-macros","version":"1.2.0","source":"registry+https://github.com/rust-lang/crates.io-index"},{"name":"winapi","version":"0.3.9","source":"registry+https://github.com/rust-lang/crates.io-index"}],"replace":null},"advisory":null,"versions":null}]}}
--- end ---
[DNM] there are no updates
$ git add .
--- stdout ---

--- end ---
$ git commit -F /tmp/tmpacq2zg4j
--- stdout ---
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

--- end ---
Source code is licensed under the AGPL.