This project contains known security vulnerabilities. Find detailed information at the bottom.
yup-oauth2(19 total, 8 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.38 | 1.0.104 | up to date |
| async-trait | ^0.1 | 0.1.92 | up to date |
| base64 | ^0.13.0 | 0.23.1 | out of date |
| futures | ^0.3 | 0.3.34 | up to date |
| http | ^0.2 | 1.5.0 | out of date |
| hyper | ^0.14 | 1.11.1 | out of date |
| hyper-rustls | ^0.23 | 0.27.10 | out of date |
| hyper-tls | ^0.5.0 | 0.6.0 | out of date |
| itertools | ^0.10.0 | 0.15.0 | out of date |
| log | ^0.4 | 0.4.34 | up to date |
| percent-encoding | ^2 | 2.3.2 | up to date |
| rustls ⚠️ | ^0.20.4 | 0.23.45 | insecure |
| rustls-pemfile | ^0.3 | 2.2.0 | out of date |
| seahash | ^4 | 4.1.0 | up to date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| time | ^0.3.7 | 0.3.55 | up to date |
| tokio | ^1.0 | 1.53.1 | up to date |
| url | ^2 | 2.5.8 | up to date |
(5 total, 4 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.7 | 0.11.11 | out of date |
| httptest | ^0.14 | 0.16.4 | out of date |
| hyper-rustls | ^0.23 | 0.27.10 | out of date |
| tempfile | ^3.1 | 3.27.0 | up to date |
| webbrowser ⚠️ | ^0.5 | 1.2.4 | insecure |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
webbrowser: Unix `BROWSER` handling allows browser argument injectionOn Unix platforms handled by src/unix.rs, affected versions substitute the
caller-supplied URL into the BROWSER environment-variable template before
tokenizing the resulting string with split_ascii_whitespace(). If an
application passes an attacker-controlled non-HTTP(S) URL whose parsed form
retains spaces and the effective BROWSER template contains %s, text that
should remain within one URL argument becomes additional browser arguments.
The issue was reproduced with Chromium by injecting
--remote-debugging-port, which exposed a local DevTools endpoint, and
--proxy-server, which redirected browser traffic through an
attacker-controlled proxy. The available arguments and resulting impact depend
on the browser launched by the affected application.
Version 1.2.2 fixes the issue by tokenizing the BROWSER template before
substituting the URL, preserving the URL as part of a single argument. Users
should upgrade to version 1.2.2 or later. Applications that only need HTTP(S)
URLs can also enable the crate's hardened feature as defense in depth.
This issue was reported by @dywzju09-blip.