Skip to content

0.10.1

Latest

Choose a tag to compare

@benoitc benoitc released this 18 Nov 14:16
· 20 commits to main since this release
7a11f21

A security fix for WASI 0.2 and 0.3 file paths, and the test suites a
contributor fetches are now always the pinned ones.

Security

  • Fixed: a WASI 0.2 or 0.3 path with a NUL byte acted on a shorter name.
    Only opening a file refused a path containing a NUL byte. Creating a
    directory, removing, renaming or linking a file, making a symbolic link,
    reading or changing a file's details all acted on the part of the name
    before the NUL, so a guest asking for made followed by a NUL and more
    created made. It stayed inside the directories the guest was granted.
    Such a path is now refused as invalid in every WASI version, and the
    native file backend refuses one as well. WASI preview 1 was not affected.

Changes

  • The upstream test suites are always the pinned ones. The scripts that
    fetch the specification suites and wasmtime's test programs used an
    existing checkout without looking at its commit, so a local conformance
    run could test a different suite than the one this project declares, and
    changing a pin did nothing to a checkout you already had. Now a checkout
    at another commit is moved to the pin, and the script stops if you
    changed files in it.