{"id":"GHSA-r64r-5h43-26qv","revision":null,"records":[{"revision":"3895ff6456504e69a9a85ad4d6d06be0","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-23649","aliases":[],"title":"Any authenticated user may obtain private message details from other users on the same instance","description":"Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a private message report contains the private message itself, which means any user can just iterate over message ids to (loudly) obtain all private messages of an instance. A user with instance admin privileges can also abuse this if the private message is removed from the response, as they're able to see the resulting reports.\n\nCreating a private message report by POSTing to `/api/v3/private_message/report` does not validate whether the reporter is the recipient of the message. lemmy-ui does not allow the sender to report the message; the API method should likely be restricted to accessible to recipients only. The API response when creating a report contains the `private_message_report_view` with all the details of the report, including the private message that has been reported:\n\nAny authenticated user can obtain arbitrary (untargeted) private message contents. Privileges required depend on the instance configuration; when registrations are enabled without application system, the privileges required are practically none. When registration applications are required, privileges required could be considered low, but this assessment heavily varies by instance.\n\nVersion 0.19.1 contains a patch for this issue. A workaround is available. If an update to a fixed Lemmy version is not immediately possible, the API route can be blocked in the reverse proxy. This will prevent anyone from reporting private messages, but it will also prevent exploitation before the update has been applied.","state":0,"publishedAt":"2024-01-24T18:09:30.401+00:00","modifiedAt":"2025-05-30T14:16:25.819+00:00","affected":[{"ecosystem":"Vendor product","name":"lemmy","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"LemmyNet\",\n                    \"product\": \"lemmy\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 0.17.0, < 0.19.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":7.5,"severity":"HIGH"}],"references":["https://github.com/LemmyNet/lemmy/security/advisories/GHSA-r64r-5h43-26qv","https://github.com/LemmyNet/lemmy/commit/bc32b408b523b9b64aa57b8e47748f96cce0dae5"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-23649","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-23649","identifiers":["CVE-2024-23649"]},"retained":false,"historicalAffected":[]},{"revision":"d14f26de6a554f08aa2e5a6b0316035e","observedAt":"2026-11-15T01:49:16.246+00:00","statement":{"source":"euvd","id":"EUVD-2024-0411","aliases":["CVE-2024-23649","GHSA-r64r-5h43-26qv"],"title":"Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a…","description":"Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a private message report contains the private message itself, which means any user can just iterate over message ids to (loudly) obtain all private messages of an instance. A user with instance admin privileges can also abuse this if the private message is removed from the response, as they're able to see the resulting reports.\n\nCreating a private message report by POSTing to `/api/v3/private_message/report` does not validate whether the reporter is the recipient of the message. lemmy-ui does not allow the sender to report the message; the API method should likely be restricted to accessible to recipients only. The API response when creating a report contains the `private_message_report_view` with all the details of the report, including the private message that has been reported:\n\nAny authenticated user can obtain arbitrary (untargeted) private message contents. Privileges required depend on the instance configuration; when registrations are enabled without application system, the privileges required are practically none. When registration applications are required, privileges required could be considered low, but this assessment heavily varies by instance.\n\nVersion 0.19.1 contains a patch for this issue. A workaround is available. If an update to a fixed Lemmy version is not immediately possible, the API route can be blocked in the reverse proxy. This will prevent anyone from reporting private messages, but it will also prevent exploitation before the update has been applied.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":7.5,"severity":null}],"references":["https://github.com/LemmyNet/lemmy/security/advisories/GHSA-r64r-5h43-26qv","https://github.com/LemmyNet/lemmy/commit/bc32b408b523b9b64aa57b8e47748f96cce0dae5"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-0411","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Jan 24, 2024, 6:09:30 PM","dateUpdated":"May 30, 2025, 2:16:25 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2024-0411","identifiers":["EUVD-2024-0411","CVE-2024-23649","GHSA-r64r-5h43-26qv"]},"retained":false,"historicalAffected":[]},{"revision":"02b561f61393480ebc507012d62260a3","observedAt":"2026-10-24T23:17:22.571+00:00","statement":{"source":"nvd","id":"CVE-2024-23649","aliases":[],"title":"Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a…","description":"Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a private message report contains the private message itself, which means any user can just iterate over message ids to (loudly) obtain all private messages of an instance. A user with instance admin privileges can also abuse this if the private message is removed from the response, as they're able to see the resulting reports.\n\nCreating a private message report by POSTing to `/api/v3/private_message/report` does not validate whether the reporter is the recipient of the message. lemmy-ui does not allow the sender to report the message; the API method should likely be restricted to accessible to recipients only. The API response when creating a report contains the `private_message_report_view` with all the details of the report, including the private message that has been reported:\n\nAny authenticated user can obtain arbitrary (untargeted) private message contents. Privileges required depend on the instance configuration; when registrations are enabled without application system, the privileges required are practically none. When registration applications are required, privileges required could be considered low, but this assessment heavily varies by instance.\n\nVersion 0.19.1 contains a patch for this issue. A workaround is available. If an update to a fixed Lemmy version is not immediately possible, the API route can be blocked in the reverse proxy. This will prevent anyone from reporting private messages, but it will also prevent exploitation before the update has been applied.","state":0,"publishedAt":"2024-01-24T18:15:09.103+00:00","modifiedAt":"2026-06-17T07:13:18.353+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":7.5,"severity":"HIGH"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/LemmyNet/lemmy/commit/bc32b408b523b9b64aa57b8e47748f96cce0dae5","https://github.com/LemmyNet/lemmy/security/advisories/GHSA-r64r-5h43-26qv"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-23649","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-200","CWE-285","NVD-CWE-noinfo"],"productCriteria":["cpe:2.3:a:join-lemmy:lemmy:*:*:*:*:*:rust:*:*"],"sourceDates":{"published":"2024-01-24T18:15:09.103","lastModified":"2026-06-17T07:13:18.353"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2024-23649","identifiers":["CVE-2024-23649"]},"retained":false,"historicalAffected":[]},{"revision":"a1120d0bbaef4a84b5c790148b805714","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-r64r-5h43-26qv","aliases":["CVE-2024-23649"],"title":"Any authenticated user may obtain private message details from other users on the same instance","description":"### Summary\nUsers can report private messages, even when they're neither sender nor recipient of the message.\nThe API response to creating a private message report contains the private message itself, which means any user can just iterate over message ids to (loudly) obtain all private messages of an instance.\nA user with instance admin privileges can also abuse this if the private message is removed from the response, as they're able to see the resulting reports.\n\n### Details\nCreating a private message report by POSTing to `/api/v3/private_message/report` does not validate whether the reporter is the recipient of the message.\nAt least lemmy-ui does not allow the sender to report the message; the API method should likely be restricted to accessible to recipients only.\nThe API response when creating a report contains the `private_message_report_view` with all the details of the report, including the private message that has been reported:\n<details>\n\n<summary>Example response</summary>\n\nIn the report below, the creator with id 3 is different from the private message creator (id 2) and private message recipient (id 6).\n\n```json\n{\n  \"private_message_report_view\": {\n    \"private_message_report\": {\n      \"id\": 14,\n      \"creator_id\": 3,\n      \"private_message_id\": 7,\n      \"original_pm_text\": \"testfoo\",\n      \"reason\": \"reporting id 7\",\n      \"resolved\": false,\n      \"published\": \"2023-12-15T19:23:03.441967Z\"\n    },\n    \"private_message\": {\n      \"id\": 7,\n      \"creator_id\": 2,\n      \"recipient_id\": 6,\n      \"content\": \"testfoo\",\n      \"deleted\": false,\n      \"read\": false,\n      \"published\": \"2023-12-15T19:21:41.920872Z\",\n      \"ap_id\": \"https://1b1w56.lem.rocks/private_message/7\",\n      \"local\": true\n    },\n    \"private_message_creator\": {\n      \"id\": 2,\n      \"name\": \"admin\",\n      \"banned\": false,\n      \"published\": \"2023-12-14T23:45:05.055427Z\",\n      \"actor_id\": \"https://1b1w56.lem.rocks/u/admin\",\n      \"local\": true,\n      \"deleted\": false,\n      \"bot_account\": false,\n      \"instance_id\": 1\n    },\n    \"creator\": {\n      \"id\": 3,\n      \"name\": \"testuser1\",\n      \"banned\": false,\n      \"published\": \"2023-12-14T23:47:57.571772Z\",\n      \"actor_id\": \"https://1b1w56.lem.rocks/u/testuser1\",\n      \"local\": true,\n      \"deleted\": false,\n      \"bot_account\": false,\n      \"instance_id\": 1\n    }\n  }\n}\n```\n\n</details>\n\nIf these details were not available in the response, but reports could still be created by any user, or at least by any admin, this would allow an instance admin to create reports and obtain the message contents from the report system.\n\nThis was originally discovered from incorrect reports on a 0.18.5 instance and has been replicated in a 0.19.0 test environment.\n\n### PoC\n\n```bash\ncurl -v 'https://myinstance.tld/api/v3/private_message/report' -X POST -H 'Content-Type: application/json' -H 'authorization: Bearer ...' --data-raw '{\"private_message_id\":1,\"reason\":\"i like reports\"}'\n```\n\n### Impact\nAny authenticated user can obtain arbitrary (untargeted) private message contents.\nPrivileges required depend on the instance configuration; when registratons are enabled without application system, the privileges required are practically none.\nWhen registration applications are required, privileges required could be considered low, but this assessment heavily varies by instance.\n\n### Detection\n\nAny private message reports where the report creator is not equal to the private message recipient may be an attempt to exploit this.\nAs this was originally discovered from an incorrect report, likely related to a bug in a client app, it should be noted that not all mismatching reports should be considered malicious; though a frequent occurrence of them likely indicates an exploitation attempt.\n\n### Workaround when updating is not immediately possible\n\nIf an update to a fixed Lemmy version is not immediately possible, the API route can be blocked in the reverse proxy.\nThis will prevent anyone from reporting private messages, but it will also prevent exploitation before the update has been applied.\n\nnginx example:\n```nginx\nlocation = /api/v3/private_message/report {\n  default_type application/json;\n  return 403 '{\"error\":\"couldnt_create_report\"}';\n}\n```","state":0,"publishedAt":"2024-01-24T21:13:39+00:00","modifiedAt":"2026-09-10T03:50:05.1641218+00:00","affected":[{"ecosystem":"crates.io","name":"lemmy_server","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.17.0"},{"kind":"fixed","version":"0.19.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/LemmyNet/lemmy/security/advisories/GHSA-r64r-5h43-26qv","https://nvd.nist.gov/vuln/detail/CVE-2024-23649","https://github.com/LemmyNet/lemmy/commit/bc32b408b523b9b64aa57b8e47748f96cce0dae5","https://github.com/LemmyNet/lemmy"],"sourceUrl":"https://github.com/advisories/GHSA-r64r-5h43-26qv","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-r64r-5h43-26qv","identifiers":["GHSA-r64r-5h43-26qv","CVE-2024-23649"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T14:44:51.0354681+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T14:44:51.0354681+00:00","lastSuccessAt":"2026-11-16T14:44:51.2191988+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.2191997+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-c7e42aebd80e0c2307ddc550ecef29877d1c8891eaea04fabfc75498ab1ffe9c","complete":true,"records":426004,"lastAttemptAt":"2026-11-16T14:44:50.7345962+00:00","lastSuccessAt":"2026-11-16T14:44:50.6847077+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.7345962+00:00","snapshotPublishedAt":"2026-11-16T14:31:19+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-e7b8d43557f44ad0b4e0a87d8bc9833b","complete":true,"records":13821,"lastAttemptAt":"2026-11-16T14:45:17.0377344+00:00","lastSuccessAt":"2026-11-16T13:45:32.439+00:00","error":null,"lastVerifiedAt":"2026-11-16T13:45:32.439+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13874,"expectedIdentifiers":13874,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T14:44:51.0354681+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T14:44:51.0354681+00:00","lastSuccessAt":"2026-11-16T14:44:51.2200779+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.2200784+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-4b206dc3f3fc4572b101aa266f730110","complete":false,"records":13833,"lastAttemptAt":"2026-11-16T14:45:16.4505777+00:00","lastSuccessAt":"2026-11-16T14:45:16.447+00:00","error":"300 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T14:45:16.447+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13574,"expectedIdentifiers":13874,"failedIdentifiers":300},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T14:44:50.9903861+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.9903861+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T14:44:50.781369+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.781369+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T14:44:51.0024803+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:51.0024803+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-263d9c8d63997345727b11314d9b9377eba9fd4146f04497c069a15e332b60cb","complete":true,"records":232482,"lastAttemptAt":"2026-11-16T14:44:50.8876074+00:00","lastSuccessAt":"2026-11-16T07:32:30.5701252+00:00","error":null,"lastVerifiedAt":"2026-11-16T14:44:50.8876074+00:00","snapshotPublishedAt":"2026-11-16T06:48:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}