Skip to content
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.

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

RUSTSEC-2021-0145: Potential unaligned read #167

Closed
github-actions bot opened this issue Oct 13, 2024 · 3 comments
Closed

RUSTSEC-2021-0145: Potential unaligned read #167

github-actions bot opened this issue Oct 13, 2024 · 3 comments

Comments

@github-actions
Copy link

Potential unaligned read

Details
Status unsound
Package atty
Version 0.2.14
URL softprops/atty#50
Date 2021-07-04

On windows, atty dereferences a potentially unaligned pointer.

In practice however, the pointer won't be unaligned unless a custom global allocator is used.

In particular, the System allocator on windows uses HeapAlloc, which guarantees a large enough alignment.

atty is Unmaintained

A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.

Last release of atty was almost 3 years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

See advisory page for additional details.

@Lut99
Copy link
Member

Lut99 commented Oct 14, 2024

Wait didn't we already look at this? Or was that at the policy-reasoner?

@DanielVoogsgerd
Copy link
Member

DanielVoogsgerd commented Oct 14, 2024

Yes, we did look at this (#133). That issue was about it being unmaintained, but now it's also potentially vulnerable; great combination. 😅

To summarize the status. We have to merge #140, #165, and then merge the pull request Dependabot should provide us.

@Lut99
Copy link
Member

Lut99 commented Oct 15, 2024

OK, #140 and #165 are merged. Now waiting for that sweet Dependabot PR...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants