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.

Crate imageflow_helpers

Dependencies

(21 total, 1 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 libc^0.20.2.162up to date
 time ⚠️*0.3.36maybe insecure
 chrono ⚠️^0.40.4.38maybe insecure
 serde*1.0.214up to date
 serde_json*1.0.132up to date
 serde_derive*1.0.214up to date
 lazy_static^11.5.0up to date
 twox-hash^12.0.1out of date
 fnv*1.0.7up to date
 blake2-rfc*0.2.18up to date
 sha2*0.10.8up to date
 digest*0.10.7up to date
 uuid*1.11.0up to date
 smallvec ⚠️*1.13.2maybe insecure
 regex ⚠️^11.11.1maybe insecure
 rand*0.8.5up to date
 rgb^0.80.8.50up to date
 base64^0.220.22.1up to date
 zip^22.2.0up to date
 unicase^22.8.0up to date
 backtrace^0.30.3.74up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 mockito*1.5.0up to date

Crate imageflow_http_helpers

Dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 reqwest^0.12.70.12.9up to date
 tokio ⚠️^11.41.1maybe insecure

Crate imageflow_types

Dependencies

(8 total, 2 possibly insecure)

CrateRequiredLatestStatus
 serde^11.0.214up to date
 serde_json^11.0.132up to date
 serde_derive^11.0.214up to date
 lazy_static^11.5.0up to date
 regex ⚠️^11.11.1maybe insecure
 chrono ⚠️^0.40.4.38maybe insecure
 imgref^1.101.11.0up to date
 rgb^0.80.8.50up to date

Build dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 quick-error^22.0.1up to date
 chrono ⚠️^0.40.4.38maybe insecure

Crate imageflow_riapi

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 url*2.5.3up to date
 ieee754^0.20.2.6up to date
 time ⚠️*0.3.36maybe insecure
 option-filter^11.0.2up to date
 lazy_static^11.5.0up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 difference^22.0.0up to date

Crate imageflow_core

Dependencies

(42 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 libc^0.20.2.162up to date
 num^0.40.4.3up to date
 time^0.30.3.36up to date
 chrono ⚠️^0.40.4.38maybe insecure
 serde^11.0.214up to date
 serde_json^11.0.132up to date
 serde_derive^11.0.214up to date
 lazy_static^11.5.0up to date
 twox-hash^12.0.1out of date
 fnv^11.0.7up to date
 blake2-rfc^0.20.2.18up to date
 threadpool^11.8.1up to date
 petgraph^0.60.6.5up to date
 daggy^0.80.8.0up to date
 smallvec ⚠️^11.13.2maybe insecure
 itertools^0.130.13.0up to date
 imgref^1.4.11.11.0up to date
 slotmap^11.0.7up to date
 base64^0.220.22.1up to date
 hex^0.40.4.3up to date
 gif^0.13.10.13.1up to date
 rgb^0.80.8.50up to date
 imagequant^44.3.3up to date
 lodepng^33.10.7up to date
 flate2^1.01.0.34up to date
 libwebp-sys ⚠️^0.90.11.0out of date
 libz-sys^11.1.20up to date
 zune-bmp^0.5.0-rc40.4.0up to date
 bytemuck^11.19.0up to date
 jpeg-decoder^0.3.10.3.1up to date
 lcms2^66.1.0up to date
 lcms2-sys^44.0.5up to date
 chashmap^2.22.2.2up to date
 getopts^0.20.2.21up to date
 byteorder^11.5.0up to date
 url^22.5.3up to date
 uuid^11.11.0up to date
 mozjpeg^0.100.10.10up to date
 multiversion^0.7.40.7.4up to date
 mozjpeg-sys^22.2.1up to date
 evalchroma^11.0.3up to date
 libpng-sys^1.1.91.1.9up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 hyper^1.41.5.0up to date
 dssim^3.33.3.2up to date
 criterion^0.50.5.1up to date
 rand*0.8.5up to date

Crate imageflow_abi

Dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 libc^0.20.2.162up to date
 backtrace*0.3.74up to date
 smallvec ⚠️*1.13.2maybe insecure
 base64^0.220.22.1up to date

Build dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 cbindgen^0.270.27.0up to date
 regex ⚠️^11.11.1maybe insecure

Crate imageflow

No external dependencies! 🙌

Crate imageflow_tool_lib

Dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 libc^0.20.2.162up to date
 clap^44.5.20up to date
 time^0.30.3.36up to date
 threadpool^11.8.1up to date
 serde^11.0.214up to date
 serde_json^11.0.132up to date

Crate imageflow_c_components

Dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 mozjpeg-sys^22.2.1up to date
 libc0.2.*0.2.162up to date
 libz-sys^1.0.181.1.20up to date
 libpng-sys^1.1.81.1.9up to date
 lcms2-sys^44.0.5up to date

Build dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 glob^0.3.00.3.1up to date
 cc^11.1.36up to date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.

The affected functions from time 0.2.7 through 0.2.22 are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • time::at_utc
  • time::at
  • time::now
  • time::tzset

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending 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.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users 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.

Workarounds

A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.

Examples:

Cargo.toml:

chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }

Commandline:

cargo add chrono --no-default-features -F clock

Sources:

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The 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.

Overview

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.

Affected versions

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.

Mitigations

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.

Acknowledgements

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.

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

libwebp-sys: libwebp: OOB write in BuildHuffmanTable

RUSTSEC-2023-0061

Google and Mozilla have released security advisories for RCE due to heap overflow in libwebp. Google warns the vulnerability has been exploited in the wild.

libwebp needs to be updated to 1.3.2 to include a patch for "OOB write in BuildHuffmanTable".