mirror of
https://github.com/netbirdio/advisory-database.git
synced 2026-05-22 18:04:22 -07:00
Publish Advisories
GHSA-25hc-qcg6-38wj GHSA-55f3-3qvg-8pv5 GHSA-9hcv-j9pv-qmph GHSA-w9jx-4g6g-rp7x
This commit is contained in:
advisory-database[bot]
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-25hc-qcg6-38wj",
|
||||
"modified": "2024-06-19T15:04:41Z",
|
||||
"modified": "2024-06-19T18:38:19Z",
|
||||
"published": "2024-06-19T15:04:41Z",
|
||||
"aliases": [
|
||||
|
||||
"CVE-2024-38355"
|
||||
],
|
||||
"summary": "socket.io has an unhandled 'error' event",
|
||||
"details": "### Impact\n\nA specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.\n\n```\nnode:events:502\n throw err; // Unhandled 'error' event\n ^\n\nError [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)\n at new NodeError (node:internal/errors:405:5)\n at Socket.emit (node:events:500:17)\n at /myapp/node_modules/socket.io/lib/socket.js:531:14\n at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {\n code: 'ERR_UNHANDLED_ERROR',\n context: undefined\n}\n```\n\n### Affected versions\n\n| Version range | Needs minor update? |\n|------------------|------------------------------------------------|\n| `4.6.2...latest` | Nothing to do |\n| `3.0.0...4.6.1` | Please upgrade to `socket.io@4.6.2` (at least) |\n| `2.3.0...2.5.0` | Please upgrade to `socket.io@2.5.1` |\n\n### Patches\n\nThis issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in `socket.io@4.6.2` (released in May 2023).\n\nThe fix was backported in the 2.x branch today: https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c\n\n### Workarounds\n\nAs a workaround for the affected versions of the `socket.io` package, you can attach a listener for the \"error\" event:\n\n```js\nio.on(\"connection\", (socket) => {\n socket.on(\"error\", () => {\n // ...\n });\n});\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open a discussion [here](https://github.com/socketio/socket.io/discussions)\n\nThanks a lot to [Paul Taylor](https://github.com/Y0ursTruly) for the responsible disclosure.\n\n### References\n\n- https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115\n- https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c\n",
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-55f3-3qvg-8pv5",
|
||||
"modified": "2024-06-07T19:40:00Z",
|
||||
"modified": "2024-06-19T18:38:48Z",
|
||||
"published": "2024-06-07T19:40:00Z",
|
||||
"aliases": [
|
||||
|
||||
"CVE-2024-38358"
|
||||
],
|
||||
"summary": "Symlink bypasses filesystem sandbox",
|
||||
"details": "### Summary\n\nIf the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both `oflags::creat` and `rights::fd_write`. Programs can also crash the runtime by creating a symlink pointing outside with `path_symlink` and `path_open`ing the link.\n\n### Details\n\n\n\n### PoC\nSetup a filesystem as follows.\n\n```\n.\n├── outside.file\n└── preopen\n └── dir\n └── file -> ../../outside.file\n```\n\nCompile this Rust snippet with `wasi` v0.11 (for the preview1 API).\n\n```rust\nfn main() {\n unsafe {\n let filefd = wasi::path_open(\n 5,\n wasi::LOOKUPFLAGS_SYMLINK_FOLLOW,\n \"app/dir/file\",\n wasi::OFLAGS_CREAT,\n wasi::RIGHTS_FD_READ | wasi::RIGHTS_FD_WRITE,\n 0,\n 0,\n )\n .unwrap();\n eprintln!(\"filefd: {filefd}\");\n\n let mut buf = [0u8; 10];\n let iovs = [wasi::Iovec {\n buf: buf.as_mut_ptr(),\n buf_len: buf.len(),\n }];\n\n let read = wasi::fd_read(filefd, &iovs).unwrap();\n\n eprintln!(\"read {read}: {}\", String::from_utf8_lossy(&buf));\n }\n}\n```\n\nRun the compiled binary with Wasmer preopening `preopen/`:\n\n```\nwasmer run --mapdir /app:preopen a.wasm\n```\n\nThis should not print the contents of the `outside.file`. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.\n\n",
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-9hcv-j9pv-qmph",
|
||||
"modified": "2024-06-19T15:07:08Z",
|
||||
"modified": "2024-06-19T18:38:28Z",
|
||||
"published": "2024-06-19T15:07:08Z",
|
||||
"aliases": [
|
||||
|
||||
"CVE-2024-38356"
|
||||
],
|
||||
"summary": "TinyMCE Cross-Site Scripting (XSS) vulnerability using noneditable_regexp option",
|
||||
"details": "### Impact\nA [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) vulnerability was discovered in TinyMCE’s content extraction code. When using the `noneditable_regexp` option, specially crafted HTML attributes containing malicious code were able to be executed when content was extracted from the editor.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 7.2.0, TinyMCE 6.8.4 and TinyMCE 5.11.0 LTS by ensuring that, when using the `noneditable_regexp` option, any content within an attribute is properly verified to match the configured regular expression before being added.\n\n### Fix\nTo avoid this vulnerability:\n\n* Upgrade to TinyMCE 7.2.0 or higher.\n* Upgrade to TinyMCE 6.8.4 or higher for TinyMCE 6.x.\n* Upgrade to TinyMCE 5.11.0 LTS or higher for TinyMCE 5.x (only available as part of commercial [long-term support](https://www.tiny.cloud/long-term-support/) contract).\n\n### References\n* [TinyMCE 6.8.4](https://www.tiny.cloud/docs/tinymce/6/6.8.4-release-notes/#overview)\n* [TinyMCE 7.2.0](https://www.tiny.cloud/docs/tinymce/7/7.2-release-notes/#overview)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)",
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-w9jx-4g6g-rp7x",
|
||||
"modified": "2024-06-19T15:07:03Z",
|
||||
"modified": "2024-06-19T18:38:37Z",
|
||||
"published": "2024-06-19T15:07:03Z",
|
||||
"aliases": [
|
||||
|
||||
"CVE-2024-38357"
|
||||
],
|
||||
"summary": "TinyMCE Cross-Site Scripting (XSS) vulnerability using noscript elements",
|
||||
"details": "### Impact\nA [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) vulnerability was discovered in TinyMCE’s content parsing code. This allowed specially crafted noscript elements containing malicious code to be executed when that content was loaded into the editor.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 7.2.0, TinyMCE 6.8.4 and TinyMCE 5.11.0 LTS by ensuring that content within noscript elements are properly parsed.\n\n### Fix\nTo avoid this vulnerability:\n\n* Upgrade to TinyMCE 7.2.0 or higher.\n* Upgrade to TinyMCE 6.8.4 or higher for TinyMCE 6.x.\n* Upgrade to TinyMCE 5.11.0 LTS or higher for TinyMCE 5.x (only available as part of commercial [long-term support](https://www.tiny.cloud/long-term-support/) contract).\n\n### Acknowledgements\nTiny thanks [Malav Khatri](https://malavkhatri.com/) and another reporter for their help identifying this vulnerability.\n\n### References\n* [TinyMCE 6.8.4](https://www.tiny.cloud/docs/tinymce/6/6.8.4-release-notes/#overview)\n* [TinyMCE 7.2.0](https://www.tiny.cloud/docs/tinymce/7/7.2-release-notes/#overview)\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)\n",
|
||||
|
||||
Reference in New Issue
Block a user