Publish Advisories

GHSA-ff4p-7xrq-q5r8
GHSA-xm67-587q-r2vw
GHSA-ch89-5g45-qwc7
GHSA-h84q-m8rr-3v9q
This commit is contained in:
advisory-database[bot]
2025-05-02 12:53:24 +00:00
parent a8cfb39207
commit c520d18be0
4 changed files with 23 additions and 7 deletions
File diff suppressed because one or more lines are too long
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-xm67-587q-r2vw",
"modified": "2023-03-09T00:09:03Z",
"modified": "2025-05-02T12:52:23Z",
"published": "2023-03-09T00:09:03Z",
"aliases": [
"CVE-2023-27477"
@@ -158,6 +158,10 @@
{
"type": "WEB",
"url": "https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/Mov-ItrNJsQ"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2023-0093.html"
}
],
"database_specific": {
File diff suppressed because one or more lines are too long
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-h84q-m8rr-3v9q",
"modified": "2024-02-01T00:15:47Z",
"modified": "2025-05-02T12:51:45Z",
"published": "2024-02-01T00:15:47Z",
"aliases": [
"CVE-2022-39394"
],
"summary": "wasmtime_trap_code C API function has out of bounds write vulnerability",
"details": "### Impact\n\nThere is a bug in Wasmtime's C API implementation where the definition of the `wasmtime_trap_code` does not match its declared signature in the `wasmtime/trap.h` header file. This discrepancy causes the function implementation to perform a 4-byte write into a 1-byte buffer provided by the caller. This can lead to three zero bytes being written beyond the 1-byte location provided by the caller.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime 2.0.2.\n\n### Workarounds\n\nThis can be worked around by providing a 4-byte buffer casted to a 1-byte buffer when calling `wasmtime_trap_code`. Users of the `wasmtime` crate are not affected by this issue, only users of the C API function `wasmtime_trap_code` are affected.\n\n### References\n\n* [Definition of `wasmtime_trap_code`](https://docs.wasmtime.dev/c-api/trap_8h.html#a6580f4f209d3eaebb6e8b9a901a30b7a)\n* [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA)\n* [Patch to fix for `main` branch](https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)\n\n",
"details": "### Impact\n\nThere is a bug in Wasmtime's C API implementation where the definition of the `wasmtime_trap_code` does not match its declared signature in the `wasmtime/trap.h` header file. This discrepancy causes the function implementation to perform a 4-byte write into a 1-byte buffer provided by the caller. This can lead to three zero bytes being written beyond the 1-byte location provided by the caller.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime 2.0.2.\n\n### Workarounds\n\nThis can be worked around by providing a 4-byte buffer casted to a 1-byte buffer when calling `wasmtime_trap_code`. Users of the `wasmtime` crate are not affected by this issue, only users of the C API function `wasmtime_trap_code` are affected.\n\n### References\n\n* [Definition of `wasmtime_trap_code`](https://docs.wasmtime.dev/c-api/trap_8h.html#a6580f4f209d3eaebb6e8b9a901a30b7a)\n* [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA)\n* [Patch to fix for `main` branch](https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)",
"severity": [
{
"type": "CVSS_V3",
@@ -78,6 +78,10 @@
{
"type": "WEB",
"url": "https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0097.html"
}
],
"database_specific": {