Skip to content

Commit e841a33

Browse files
advisory-database[bot]advisory-database[bot]
committed
Publish Advisories
GHSA-2c28-m2m7-mf55 GHSA-hmgw-9jrg-hf2m GHSA-w4m2-qmh3-2g8f
1 parent 8823f27 commit e841a33

File tree

3 files changed

+140
-10
lines changed

3 files changed

+140
-10
lines changed

‎advisories/unreviewed/2023/10/GHSA-2c28-m2m7-mf55/GHSA-2c28-m2m7-mf55.json‎ renamed to ‎advisories/github-reviewed/2023/10/GHSA-2c28-m2m7-mf55/GHSA-2c28-m2m7-mf55.json‎

Lines changed: 36 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-2c28-m2m7-mf55",
4-
"modified": "2023-10-16T00:30:26Z",
4+
"modified": "2023-10-19T20:01:32Z",
55
"published": "2023-10-16T00:30:26Z",
66
"aliases": [
77
"CVE-2023-5588"
88
],
9+
"summary": "Pleroma Path Traversal vulnerability",
910
"details": "A vulnerability was found in kphrx pleroma. It has been classified as problematic. This affects the function Pleroma.Emoji.Pack of the file lib/pleroma/emoji/pack.ex. The manipulation of the argument name leads to path traversal. The complexity of an attack is rather high. The exploitability is told to be difficult. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 2c795094535537a8607cc0d3b7f076a609636f40. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-242187.",
1011
"severity": [
1112
{
@@ -14,7 +15,30 @@
1415
}
1516
],
1617
"affected": [
17-
18+
{
19+
"package": {
20+
"ecosystem": "Hex",
21+
"name": "pleroma"
22+
},
23+
"ecosystem_specific": {
24+
"affected_functions": [
25+
""
26+
]
27+
},
28+
"ranges": [
29+
{
30+
"type": "ECOSYSTEM",
31+
"events": [
32+
{
33+
"introduced": "0"
34+
},
35+
{
36+
"fixed": "2.5.3"
37+
}
38+
]
39+
}
40+
]
41+
}
1842
],
1943
"references": [
2044
{
@@ -29,6 +53,14 @@
2953
"type": "WEB",
3054
"url": "https://github.com/kphrx/pleroma/commit/2c795094535537a8607cc0d3b7f076a609636f40"
3155
},
56+
{
57+
"type": "PACKAGE",
58+
"url": "https://github.com/kphrx/pleroma/"
59+
},
60+
{
61+
"type": "WEB",
62+
"url": "https://github.com/kphrx/pleroma/commits/v2.5.3"
63+
},
3264
{
3365
"type": "WEB",
3466
"url": "https://vuldb.com/?ctiid.242187"
@@ -43,8 +75,8 @@
4375
"CWE-22"
4476
],
4577
"severity": "LOW",
46-
"github_reviewed": false,
47-
"github_reviewed_at": null,
78+
"github_reviewed": true,
79+
"github_reviewed_at": "2023-10-19T20:01:32Z",
4880
"nvd_published_at": null
4981
}
5082
}

‎advisories/github-reviewed/2023/10/GHSA-hmgw-9jrg-hf2m/GHSA-hmgw-9jrg-hf2m.json‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-hmgw-9jrg-hf2m",
4+
"modified": "2023-10-19T20:02:04Z",
5+
"published": "2023-10-19T20:02:04Z",
6+
"aliases": [
7+
"CVE-2023-45820"
8+
],
9+
"summary": "Directus crashes on invalid WebSocket message",
10+
"details": "### Summary\nIt seems that any Directus installation that has websockets enabled can be crashed if the websocket server receives an invalid frame. This could probably be posted as an issue and I might even be able to put together a pull request for a fix (if only I had some extra time...), but I decided to instead post as a vulnerability just for the maintainers, since this seemingly can be used to crash any live Directus server if websockets are enabled, so public disclosure is not a good idea until the issue is fixed.\n\n### Details\nThe fix for this seems quite simple; the websocket server just needs to properly catch the error instead of crashing the server. See for example: https://github.com/websockets/ws/issues/2098\n\n### PoC\n- Start a fresh Directus server (using for example the compose file here: https://docs.directus.io/self-hosted/docker-guide.html). Enable websockets by setting `WEBSOCKETS_ENABLED: 'true'` environment variable.\n- run a separate node app somewhere else to send an invalid frame to the server:\n\n```\nconst WebSocket = require(\"ws\");\nconst websocket = new WebSocket(\"ws://0.0.0.0:8055/websocket\");\nwebsocket.on(\"open\", function () {\n const chunk = Buffer.from(\"a180\", \"hex\");\n websocket._socket.write(chunk);\n});\n```\n\n### Impact\nThe server crashes with an error: `RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear`. Server needs to be manually restarted to get back online (if there's no recovery mechanism in place, as there often isn't with simple node servers). This was confirmed on a local server, and additionally I was able to crash our staging server with the same code, just pointing to our staging Directus server running at fly.io. It seems to also crash servers running in the [directus.cloud](https://directus.cloud) service. I created https://websocket-test.directus.app/, pointed the above script to the websocket url of that instance and the server does crash for a while. It seems that in there there's a mechanism for bringing the server back up quite fast, but it would be quite trivial for anyone to DoS any server running in directus.cloud by just spamming these invalid frames to the server. ",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "directus"
22+
},
23+
"ecosystem_specific": {
24+
"affected_functions": [
25+
""
26+
]
27+
},
28+
"ranges": [
29+
{
30+
"type": "ECOSYSTEM",
31+
"events": [
32+
{
33+
"introduced": "10.4.0"
34+
},
35+
{
36+
"fixed": "10.6.2"
37+
}
38+
]
39+
}
40+
]
41+
}
42+
],
43+
"references": [
44+
{
45+
"type": "WEB",
46+
"url": "https://github.com/directus/directus/security/advisories/GHSA-hmgw-9jrg-hf2m"
47+
},
48+
{
49+
"type": "WEB",
50+
"url": "https://github.com/directus/directus/commit/243eed781b42d6b4948ddb8c3792bcf5b44f55bb"
51+
},
52+
{
53+
"type": "PACKAGE",
54+
"url": "https://github.com/directus/directus"
55+
},
56+
{
57+
"type": "WEB",
58+
"url": "https://github.com/directus/directus/releases/tag/v10.6.2"
59+
}
60+
],
61+
"database_specific": {
62+
"cwe_ids": [
63+
64+
],
65+
"severity": "HIGH",
66+
"github_reviewed": true,
67+
"github_reviewed_at": "2023-10-19T20:02:04Z",
68+
"nvd_published_at": null
69+
}
70+
}

‎advisories/unreviewed/2023/10/GHSA-w4m2-qmh3-2g8f/GHSA-w4m2-qmh3-2g8f.json‎ renamed to ‎advisories/github-reviewed/2023/10/GHSA-w4m2-qmh3-2g8f/GHSA-w4m2-qmh3-2g8f.json‎

Lines changed: 34 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,51 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-w4m2-qmh3-2g8f",
4-
"modified": "2023-10-19T18:30:30Z",
4+
"modified": "2023-10-19T20:02:23Z",
55
"published": "2023-10-19T18:30:30Z",
66
"aliases": [
77
"CVE-2023-45277"
88
],
9+
"summary": "Yamcs Path Traversal vulnerability",
910
"details": "Yamcs 5.8.6 is vulnerable to directory traversal (issue 1 of 2). The vulnerability is in the storage functionality of the API and allows one to escape the base directory of the buckets, freely navigate system directories, and read arbitrary files.",
1011
"severity": [
1112

1213
],
1314
"affected": [
14-
15+
{
16+
"package": {
17+
"ecosystem": "Maven",
18+
"name": "org.yamcs:yamcs"
19+
},
20+
"ecosystem_specific": {
21+
"affected_functions": [
22+
""
23+
]
24+
},
25+
"ranges": [
26+
{
27+
"type": "ECOSYSTEM",
28+
"events": [
29+
{
30+
"introduced": "0"
31+
},
32+
{
33+
"fixed": "5.8.7"
34+
}
35+
]
36+
}
37+
]
38+
}
1539
],
1640
"references": [
1741
{
1842
"type": "ADVISORY",
1943
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-45277"
2044
},
45+
{
46+
"type": "PACKAGE",
47+
"url": "https://github.com/yamcs/yamcs"
48+
},
2149
{
2250
"type": "WEB",
2351
"url": "https://github.com/yamcs/yamcs/compare/yamcs-5.8.6...yamcs-5.8.7"
@@ -29,11 +57,11 @@
2957
],
3058
"database_specific": {
3159
"cwe_ids": [
32-
60+
"CWE-22"
3361
],
34-
"severity": null,
35-
"github_reviewed": false,
36-
"github_reviewed_at": null,
62+
"severity": "MODERATE",
63+
"github_reviewed": true,
64+
"github_reviewed_at": "2023-10-19T20:02:23Z",
3765
"nvd_published_at": null
3866
}
3967
}

0 commit comments

Comments
 (0)