Skip to content

Add advisory for unsound problems in workflow-core #2001

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add advisory for unsound problems in workflow-core #2001

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
277934e
Add advisory in workflow-core
safe4u Jul 7, 2024
133459c
Update versions: workflow-core still unsound in 0.18.0
safe4u Feb 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions crates/workflow-core/RUSTSEC-0000-0000.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
```toml
[advisory]
id = "RUSTSEC-0000-0000"
package = "workflow-core"
date = "2024-07-07"
url = "https://github.com/workflow-rs/workflow-rs/issues/11"
informational = "unsound"
categories = ["memory-exposure", "memory-corruption"]

[affected.functions]
"workflow_core::utils::buffer_as_slice" = ["<= 0.18.0"]
"workflow_core::utils::buffer_as_slice_mut" = ["<= 0.18.0"]

[versions]
patched = []
```

# Create illegal slice by util function

The util functions `buffer_as_slice` and `buffer_as_slice_mut` in crate
`workflow-core` are very powerful and useful to get slice of other types
but are rather unsafe as well:

1. The pointer calculation with `byte_offset` could lead to alignment problem, which is an undefined behavior.

2. The `from_raw_parts` could create an out-of-bound slice that allows the user to access or even change the memory illegally.