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.
rustodon(29 total, 12 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| dotenv | ^0.14 | 0.15.0 | out of date |
| maplit | ^1.0 | 1.0.2 | up to date |
| failure | ^0.1.6 | 0.1.8 | up to date |
| failure_derive | ^0.1.5 | 0.1.8 | up to date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| itertools | ^0.8.0 | 0.14.0 | out of date |
| structopt | ^0.2.16 | 0.3.26 | out of date |
| regex ⚠️ | ^1.3.3 | 1.12.3 | maybe insecure |
| slog | ^2.5 | 2.8.2 | up to date |
| slog-term | ^2.4 | 2.9.2 | up to date |
| slog-async | ^2.3 | 2.8.0 | up to date |
| slog-scope | ^4.1 | 4.4.1 | up to date |
| rocket-slog | ^0.4 | 0.4.0 | up to date |
| rocket | ^0.4 | 0.5.1 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| validator | ^0.9 | 0.20.0 | out of date |
| validator_derive | ^0.9 | 0.20.0 | out of date |
| askama | ^0.8.0 | 0.15.4 | out of date |
| ammonia ⚠️ | ^3.0.0 | 4.1.2 | out of date |
| diesel ⚠️ | ^1.4.3 | 2.3.6 | out of date |
| flaken | ^0.2.2 | 0.2.2 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.43 | maybe insecure |
| chrono-humanize | ^0.0.11 | 0.2.3 | out of date |
| openssl ⚠️ | ^0.10.25 | 0.10.75 | maybe insecure |
| pwhash | ^0.3 | 1.0.0 | out of date |
| base32 | ^0.4 | 0.5.1 | out of date |
| rocket_contrib | ^0.4 | 0.4.11 | up to date |
resoptNo external dependencies! 🙌
posticle(4 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ammonia ⚠️ | ^3.0 | 4.1.2 | out of date |
| maplit | ^1.0 | 1.0.2 | up to date |
| pest | ^2.1 | 2.8.6 | up to date |
| pest_derive | ^2.1 | 2.8.6 | up to date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| yaml-rust | ^0.4.3 | 0.4.5 | up to date |
| pretty_assertions | ^0.6.1 | 1.4.1 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe 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.
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.
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.
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.
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.
diesel: Binary Protocol Misinterpretation caused by Truncating or Overflowing CastsThe following presentation at this year's DEF CON was brought to our attention on the Diesel Gitter Channel:
SQL Injection isn't Dead: Smuggling Queries at the Protocol Level
http://web.archive.org/web/20240812130923/https://media.defcon.org/DEF%20CON%2032/DEF%20CON%2032%20presentations/DEF%20CON%2032%20-%20Paul%20Gerste%20-%20SQL%20Injection%20Isn't%20Dead%20Smuggling%20Queries%20at%20the%20Protocol%20Level.pdf
(Archive link for posterity.) Essentially, encoding a value larger than 4GiB can cause the length prefix in the protocol to overflow, causing the server to interpret the rest of the string as binary protocol commands or other data.
It appears Diesel does perform truncating casts in a way that could be problematic, for example: https://github.com/diesel-rs/diesel/blob/ae82c4a5a133db65612b7436356f549bfecda1c7/diesel/src/pg/connection/stmt/mod.rs#L36
This code has existed essentially since the beginning,
so it is reasonable to assume that all published versions <= 2.2.2 are affected.
The prefered migration to the outlined problem is to update to a Diesel version newer than 2.2.2, which includes fixes for the problem.
As always, you should make sure your application is validating untrustworthy user input. Reject any input over 4 GiB, or any input that could encode to a string longer than 4 GiB. Dynamically built queries are also potentially problematic if it pushes the message size over this 4 GiB bound.
For web application backends, consider adding some middleware that limits the size of request bodies by default.
Diesel now uses #[deny] directives for the following Clippy lints:
to prevent casts that will lead to precision loss or other trunctations. Additionally we performed an audit of the relevant code.
A fix is included in the 2.2.3 release.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.
ammonia: Incorrect handling of embedded SVG and MathML leads to mutation XSS after removalAffected versions of this crate did not correctly strip namespace-incompatible tags in certain situations, causing it to incorrectly account for differences between HTML, SVG, and MathML.
This vulnerability only has an effect when the svg or math tag is allowed,
because it relies on a tag being parsed as html during the cleaning process, but
serialized in a way that causes in to be parsed as xml by the browser.
Additionally, the application using this library must allow a tag that is parsed as raw text in HTML. These elements are:
Applications that do not explicitly allow any of these tags should not be affected, since none are allowed by default.