OpenSSL 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.
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.
nextcloud_appsignature(5 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.7 | 0.22.1 | out of date |
| failure | ^0.1 | 0.1.8 | up to date |
| futures | ^0.1 | 0.3.30 | out of date |
| hex | ^0.2 | 0.4.3 | out of date |
| openssl ⚠️ | ^0.9 | 0.10.64 | out of 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.