Sulkta-OSS/pallas
3
0
Fork 0
Code Issues 1 Pull requests 5 Projects Releases Packages Wiki Activity Actions

chore(deps): update rust crate rand to 0.8.6 [security] #11

Open
renovate wants to merge 1 commit from renovate/crate-rand-vulnerability into main
pull from: renovate/crate-rand-vulnerability
merge into: Sulkta-OSS:main
Conversation 0 Commits 1 Files changed 5 +5 -5
renovate commented 2026-06-28 23:24:51 -07:00
Member
Copy link

This PR contains the following updates:

Package Type Update Change
rand (source) dependencies patch 0.8.5 → 0.8.6
rand (source) dev-dependencies patch 0.8 → 0.8.6
rand (source) dependencies patch 0.8 → 0.8.6

Rand is unsound with a custom logger using rand::rng()

GHSA-cq8v-f236-94qc / RUSTSEC-2026-0097

More information

Details

It has been reported (by @​lopopolo) that the rand library is unsound (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:

  • The log and thread_rng features are enabled
  • A custom logger is defined
  • The custom logger accesses rand::rng() (previously rand::thread_rng()) and calls any TryRng (previously RngCore) methods on ThreadRng
  • The ThreadRng (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
  • Trace-level logging is enabled or warn-level logging is enabled and the random source (the getrandom crate) is unable to provide a new seed

TryRng (previously RngCore) methods for ThreadRng use unsafe code to cast *mut BlockRng<ReseedingCore> to &mut BlockRng<ReseedingCore>. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of aliased mutable references is Undefined Behaviour, the behaviour of optimized builds is hard to predict.

Severity

Low

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

Rand is unsound with a custom logger using rand::rng()

GHSA-cq8v-f236-94qc / RUSTSEC-2026-0097

More information

Details

It has been reported (by @​lopopolo) that the rand library is unsound (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:

  • The log and thread_rng features are enabled
  • A custom logger is defined
  • The custom logger accesses rand::rng() (previously rand::thread_rng()) and calls any TryRng (previously RngCore) methods on ThreadRng
  • The ThreadRng (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
  • Trace-level logging is enabled or warn-level logging is enabled and the random source (the getrandom crate) is unable to provide a new seed

TryRng (previously RngCore) methods for ThreadRng use unsafe code to cast *mut BlockRng<ReseedingCore> to &mut BlockRng<ReseedingCore>. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of aliased mutable references is Undefined Behaviour, the behaviour of optimized builds is hard to predict.

Severity

Unknown

References

This data is provided by OSV and the Rust Advisory Database (CC0 1.0).

Release Notes

rust-random/rand (rand)

v0.8.6

Compare Source

What's Changed

This release back-ports a fix from v0.10. See also #​1763.

Changes
  • Drop the experimental simd_support feature.
New Contributors

Full Changelog: https://github.com/rust-random/rand/compare/0.8.5...0.8.6

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [rand](https://rust-random.github.io/book) ([source](https://github.com/rust-random/rand)) | dependencies | patch | `0.8.5` → `0.8.6` | | [rand](https://rust-random.github.io/book) ([source](https://github.com/rust-random/rand)) | dev-dependencies | patch | `0.8` → `0.8.6` | | [rand](https://rust-random.github.io/book) ([source](https://github.com/rust-random/rand)) | dependencies | patch | `0.8` → `0.8.6` | --- ### Rand is unsound with a custom logger using rand::rng() [GHSA-cq8v-f236-94qc](https://github.com/advisories/GHSA-cq8v-f236-94qc) / [RUSTSEC-2026-0097](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) <details> <summary>More information</summary> #### Details It has been reported (by @&#8203;lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met: - The `log` and `thread_rng` features are enabled - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng` - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data) - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict. #### Severity Low #### References - [https://github.com/rust-random/rand/pull/1763](https://github.com/rust-random/rand/pull/1763) - [https://github.com/rust-random/rand](https://github.com/rust-random/rand) - [https://rustsec.org/advisories/RUSTSEC-2026-0097.html](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-cq8v-f236-94qc) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### Rand is unsound with a custom logger using `rand::rng()` [GHSA-cq8v-f236-94qc](https://github.com/advisories/GHSA-cq8v-f236-94qc) / [RUSTSEC-2026-0097](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) <details> <summary>More information</summary> #### Details It has been reported (by @&#8203;lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met: - The `log` and `thread_rng` features are enabled - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng` - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data) - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict. #### Severity Unknown #### References - [https://crates.io/crates/rand](https://crates.io/crates/rand) - [https://rustsec.org/advisories/RUSTSEC-2026-0097.html](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) - [https://github.com/rust-random/rand/pull/1763](https://github.com/rust-random/rand/pull/1763) This data is provided by [OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0097) and the [Rust Advisory Database](https://github.com/RustSec/advisory-db) ([CC0 1.0](https://github.com/rustsec/advisory-db/blob/main/LICENSE.txt)). </details> --- ### Release Notes <details> <summary>rust-random/rand (rand)</summary> ### [`v0.8.6`](https://github.com/rust-random/rand/releases/tag/0.8.6) [Compare Source](https://github.com/rust-random/rand/compare/0.8.5...0.8.6) ##### What's Changed This release back-ports a fix from v0.10. See also [#&#8203;1763]. ##### Changes - Deprecate feature `log` ([#&#8203;1772]) [#&#8203;1763]: https://github.com/rust-random/rand/pull/1763 [#&#8203;1772]: https://github.com/rust-random/rand/pull/1772 - Drop the experimental `simd_support` feature. ##### New Contributors - [@&#8203;nwalfield](https://github.com/nwalfield) made their first contribution in [#&#8203;1772](https://github.com/rust-random/rand/pull/1772) **Full Changelog**: <https://github.com/rust-random/rand/compare/0.8.5...0.8.6> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled because a matching PR was automerged previously. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMzEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjIzMS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
renovate added 1 commit 2026-06-28 23:24:52 -07:00
chore(deps): update rust crate rand to 0.8.6 [security]
Some checks failed
Validate / Check-1 (push) Failing after 1s
Details
Validate / Test Suite-1 (push) Failing after 1s
Details
Validate / Lints (push) Failing after 1s
Details
Validate / Check (push) Has been cancelled
Details
Validate / Check-2 (push) Has been cancelled
Details
Validate / Test Suite (push) Has been cancelled
Details
Validate / Test Suite-2 (push) Has been cancelled
Details
01762a7bdf
renovate scheduled this pull request to auto merge when all checks succeed 2026-06-28 23:24:53 -07:00
Some checks failed
Validate / Check-1 (push) Failing after 1s
Details
Validate / Test Suite-1 (push) Failing after 1s
Details
Validate / Lints (push) Failing after 1s
Details
Validate / Check (push) Has been cancelled
Details
Validate / Check-2 (push) Has been cancelled
Details
Validate / Test Suite (push) Has been cancelled
Details
Validate / Test Suite-2 (push) Has been cancelled
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/crate-rand-vulnerability:renovate/crate-rand-vulnerability
git checkout renovate/crate-rand-vulnerability

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff renovate/crate-rand-vulnerability
git checkout renovate/crate-rand-vulnerability
git rebase main
git checkout main
git merge --ff-only renovate/crate-rand-vulnerability
git checkout renovate/crate-rand-vulnerability
git rebase main
git checkout main
git merge --no-ff renovate/crate-rand-vulnerability
git checkout main
git merge --squash renovate/crate-rand-vulnerability
git checkout main
git merge --ff-only renovate/crate-rand-vulnerability
git checkout main
git merge renovate/crate-rand-vulnerability
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Sulkta-OSS/pallas#11
No description provided.
Delete branch "renovate/crate-rand-vulnerability"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?