This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate bracket-lib

No external dependencies! 🙌

Crate bracket-algorithm-traits

Dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 smallvec ⚠️~11.13.2maybe insecure

Crate bracket-color

Dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 serde~1.0.1101.0.215up to date
 crossterm~0.250.28.1out of date
 lazy_static^1.4.01.5.0up to date
 parking_lot~0.120.12.3up to date
 bevy~0.90.14.2out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 crossterm~0.250.28.1out of date

Crate bracket-geometry

Dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 serde~1.0.1391.0.215up to date
 specs~0.18.00.20.0out of date
 bevy~0.90.14.2out of date
 ultraviolet~0.9.00.9.2up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 crossterm~0.250.28.1out of date

Crate bracket-noise

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 crossterm~0.250.28.1out of date

Crate bracket-pathfinding

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 num-rational^0.40.4.2up to date
 rayon^1.5.01.10.0up to date
 smallvec ⚠️~11.13.2maybe insecure

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 crossterm~0.250.28.1out of date
 criterion~0.40.5.1out of date

Crate bracket-random

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 rand_xorshift^0.3.00.3.0up to date
 regex ⚠️^1.3.61.11.1maybe insecure
 lazy_static^1.4.01.5.0up to date
 serde~1.0.1101.0.215up to date
 rand^0.80.8.5up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 criterion~0.40.5.1out of date
 serde_json~1.01.0.133up to date

Crate bracket-terminal

Dependencies

(14 total, 7 outdated, 1 insecure)

CrateRequiredLatestStatus
 lazy_static^1.4.01.5.0up to date
 object-pool^0.5.30.6.0out of date
 glow~0.110.16.0out of date
 image^0.240.25.5out of date
 png^0.170.17.14up to date
 crossterm~0.250.28.1out of date
 pancurses ⚠️^0.170.17.0insecure
 ultraviolet~0.90.9.2up to date
 parking_lot~0.120.12.3up to date
 ctrlc~3.23.4.5out of date
 anyhow~1.01.0.93up to date
 wgpu^0.1323.0.0out of date
 pollster^0.20.4.0out of date
 bytemuck^1.4.01.20.0up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 criterion~0.40.5.1out of date

Crate rltk

No external dependencies! 🙌

Crate bracket-rex

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 byteorder^1.4.21.5.0up to date
 flate2^1.0.201.0.35up to date

Crate bracket-embedding

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 parking_lot~0.120.12.3up to date
 lazy_static^1.4.01.5.0up to date

Crate bracket-bevy

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 bevy^0.90.14.2out of date
 parking_lot^0.120.12.3up to date
 lazy_static^1.41.5.0up to date

Security Vulnerabilities

pancurses: Format string vulnerabilities in `pancurses`

RUSTSEC-2019-0005

pancurses::mvprintw and pancurses::printw passes a pointer from a rust &str to C, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory.

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.