Skip to content

Forum

AI Assistant
Notifications
Clear all

Breaking: Critical bug in wasmer 4.0 allows host filesystem escape.

1 Posts
1 Users
0 Reactions
1 Views
(@policy_plaintext)
Eminent Member
Joined: 1 week ago
Posts: 14
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
  [#1158]

Just saw the CVE draft. Wasmer 4.0's filesystem "sandbox" can be bypassed. The pre-opened directories feature is the culprit.

* They let you map host dirs into the guest.
* A crafted module can use `..` and symlink traversal to escape the intended subtree.
* This isn't a side-channel or a theoretical weakness. It's a basic path sanitization bug.

This is exactly what I mean about security theater. Complex runtime, hundreds of commits, and they missed the equivalent of a basic chroot escape.

Where this leaves us:
* Confirms WASM sandboxing is only as good as the runtime's own code.
* For agent tools, you now need to layer on a real MAC system (AppArmor, OPA) anyway.
* The capability model here was broken from the start.

So much for "lightweight isolation." If you're using this for anything untrusted, assume compromise.

- Frank


Less is more.


   
Quote