{"answers":{"affected":"2 open source packages ship an affected version, including matrix-sdk-crypto.","exploited":"There is no known exploitation of CVE-2024-34353 in the wild and no public exploit code.","fix":"Upgrade matrix-sdk-crypto to 0.7.1 or later.","what":"CVE-2024-34353 is a medium-severity vulnerability in matrix-org matrix-sdk-crypto, published on 13 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-34353 and fix it if it is affected.\n\nWhat it is: CVE-2024-34353 is a medium-severity vulnerability in matrix-org matrix-sdk-crypto, published on 13 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-34353 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-sdk-crypto (crates.io): affected from 0.7.0; fixed in 0.7.1\n- matrix-sdk-crypto (crates.io): affected from 0.7.0; fixed in 0.7.1\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-34353/ (Markdown: https://insights.sbomify.com/CVE-2024-34353/index.md)","id":"CVE-2024-34353","markdown":"https://insights.sbomify.com/CVE-2024-34353/index.md","name":"CVE-2024-34353","record":{"aliases":["GHSA-9ggc-845v-gcgv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Matrix Rust SDK","requires_auth":"low_privilege","summary":"An attacker with access to debug logs can read private keys for server-side key backups, compromising encrypted message security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The matrix-sdk-crypto crate, part of the Matrix Rust SDK project, is an implementation of a Matrix end-to-end encryption state machine in Rust. In Matrix, the server-side `key backup` stores encrypted copies of Matrix message keys. This facilitates key sharing between a user's devices and provides a redundant copy in case all devices are lost. The key backup uses asymmetric\ncryptography, with each server-side key backup assigned a unique public-private key pair. Due to a logic bug introduced in commit 71136e44c03c79f80d6d1a2446673bc4d53a2067, matrix-sdk-crypto version 0.7.0 will sometimes log the private part of the backup key pair to Rust debug logs (using the `tracing` crate). This issue has been resolved in matrix-sdk-crypto version 0.7.1. No known workarounds are available.","ecosystems":["crates.io"],"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-sdk-crypto contains a log exposure of private key of the server-side key backup","id":"CVE-2024-34353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":5,"next":{"headline":"CMSaasStarter: JWT Token Not Verified on Server Session","id":"CVE-2024-34354"},"packages":[{"ecosystem":"crates.io","fixed":["0.7.1"],"introduced":["0.7.0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":null,"source":"GHSA-9ggc-845v-gcgv"},{"ecosystem":"crates.io","fixed":["0.7.1"],"introduced":["0.7.0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":"pkg:cargo/matrix-sdk-crypto","source":"GHSA-9ggc-845v-gcgv"}],"prev":{"headline":"Arbitrary file write vulnerability in 1Panel","id":"CVE-2024-34352"},"products":["matrix-sdk-crypto"],"published":"2024-05-13","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-08-02","vendors":["matrix-org"]},"summary":"An attacker with access to debug logs can read private keys for server-side key backups, compromising encrypted message security.","url":"https://insights.sbomify.com/CVE-2024-34353/"}