Update vulnerable modules - #101
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughUpdates the wasmtime dependency to version 36 in balius-runtime, with corresponding bindgen! macro configuration change to use unified ChangesDependency Version Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This PR just updates dependencies which were on vulnerable versions.
The only notable change is that it updates from wasmtime 0.34 to 0.36. That's still a quite old release line, but the wasmtime maintainers backport vulnerability fixes to it. There were a lot of vulnerabilities in 0.34, some of which looked pretty exploitable on a system like balius which runs arbitrary wasm code.
There were also a few modules which specified a vulnerable patch version, I loosened those so that
cargo updatejust includes fixes for them in the future.The tests for this repo don't really work, but I ran it in my own project and it was working just fine there.
Summary by CodeRabbit