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.
native-tls(7 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| lazy_static | ^0.2 | 1.4.0 | out of date |
| libc | ^0.2 | 0.2.153 | up to date |
| openssl ⚠️ | ^0.9.23 | 0.10.64 | out of date |
| schannel | ^0.1.7 | 0.1.23 | up to date |
| security-framework | ^0.1.15 | 2.10.0 | out of date |
| security-framework-sys | ^0.1.15 | 2.10.0 | out of date |
| tempdir | ^0.3 | 0.3.7 | up to date |
openssl: `openssl` `X509NameBuilder::build` returned object is not thread safeOpenSSL has a modified bit that it can set on on X509_NAME objects. If this
bit is set then the object is not thread-safe even when it appears the code is
not modifying the value.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file readSubjectAlternativeName and ExtendedKeyUsage arguments were parsed using the OpenSSL
function X509V3_EXT_nconf. This function parses all input using an OpenSSL mini-language
which can perform arbitrary file reads.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereferenceThese functions would crash when the context argument was None with certain extension types.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.