{"answers":{"affected":"2 open source packages ship an affected version, including matrix-js-sdk.","exploited":"There is no known exploitation of CVE-2024-47080 in the wild and no public exploit code.","fix":"Upgrade matrix-js-sdk to 34.8.0 or later.","what":"CVE-2024-47080 is a high-severity vulnerability in matrix-org matrix-js-sdk, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47080 and fix it if it is affected.\n\nWhat it is: CVE-2024-47080 is a high-severity vulnerability in matrix-org matrix-js-sdk, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47080 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-js-sdk (npm): affected from 9.11.0; fixed in 34.8.0\n- matrix-js-sdk (npm): affected from 9.11.0; fixed in 34.8.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-47080/ (Markdown: https://insights.sbomify.com/CVE-2024-47080/index.md)","id":"CVE-2024-47080","markdown":"https://insights.sbomify.com/CVE-2024-47080/index.md","name":"CVE-2024-47080","record":{"aliases":["DEBIAN-CVE-2024-47080","GHSA-4jf8-g8wp-cx7c","UBUNTU-CVE-2024-47080"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Matrix JavaScript SDK","requires_auth":"none","summary":"A malicious homeserver can intercept historical message keys sent by the Matrix JavaScript SDK when using the legacy crypto stack, exposing past encrypted messages.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"matrix-js-sdk is the Matrix Client-Server SDK for JavaScript and TypeScript. In matrix-js-sdk versions versions 9.11.0 through 34.7.0, the method `MatrixClient.sendSharedHistoryKeys` is vulnerable to interception by malicious homeservers.  The method was introduced by MSC3061) and is commonly used to share historical message keys with newly invited users, granting them access to past messages in the room. However, it unconditionally sends these \"shared\" keys to all of the invited user's devices, regardless of whether the user's cryptographic identity is verified or whether the user's devices are signed by that identity. This allows the attacker to potentially inject its own devices to receive sensitive historical keys without proper security checks. Note that this only affects clients running the SDK with the legacy crypto stack. Clients using the new Rust cryptography stack (i.e. those that call `MatrixClient.initRustCrypto()` instead of `MatrixClient.initCrypto()`) are unaffected by this vulnerability, because `MatrixClient.sendSharedHistoryKeys()` raises an exception in such environments. The vulnerability was fixed in matrix-js-sdk 34.8.0 by removing the vulnerable functionality. As a workaround, remove use of affected functionality from clients.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"matrix-js-sdk keys sent via `sendSharedHistoryKeys` vulnerable to interception by malicious homeserver","id":"CVE-2024-47080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Requests vulnerable to .netrc credentials leak via malicious URLs","id":"CVE-2024-47081"},"packages":[{"ecosystem":"npm","fixed":["34.8.0"],"introduced":["9.11.0"],"last_affected":[],"package":"matrix-js-sdk","purl":null,"source":"GHSA-4jf8-g8wp-cx7c"},{"ecosystem":"npm","fixed":["34.8.0"],"introduced":["9.11.0"],"last_affected":[],"package":"matrix-js-sdk","purl":"pkg:npm/matrix-js-sdk","source":"GHSA-4jf8-g8wp-cx7c"}],"prev":{"headline":"Unauthorized usage of remote hardware module because of missing channel verification","id":"CVE-2024-47079"},"products":["matrix-js-sdk"],"published":"2024-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["matrix-org"]},"summary":"A malicious homeserver can intercept historical message keys sent by the Matrix JavaScript SDK when using the legacy crypto stack, exposing past encrypted messages.","url":"https://insights.sbomify.com/CVE-2024-47080/"}