{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-24904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-24904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24904 is a high-severity vulnerability in whisperfish libsignal-service-rs, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24904 and fix it if it is affected.\n\nWhat it is: CVE-2025-24904 is a high-severity vulnerability in whisperfish libsignal-service-rs, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-24904 in the wild and no public exploit code.\n\nAffected product: whisperfish libsignal-service-rs. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-24904/ (Markdown: https://insights.sbomify.com/CVE-2025-24904/index.md)","id":"CVE-2025-24904","markdown":"https://insights.sbomify.com/CVE-2025-24904/index.md","name":"CVE-2025-24904","record":{"aliases":["GHSA-hrrc-wpfw-5hj2"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Signal messaging library","requires_auth":"low_privilege","summary":"Attackers can inject plaintext envelopes to bypass end-to-end encryption and authentication in Signal messaging clients using this library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"libsignal-service-rs is a Rust version of the libsignal-service-java library which implements the core functionality to communicate with Signal servers. Prior to commit 82d70f6720e762898f34ae76b0894b0297d9b2f8, plaintext content envelopes could be injected by a server or a malicious client, and may have been able to bypass the end-to-end encryption and authentication. The vulnerability is fixed per 82d70f6720e762898f34ae76b0894b0297d9b2f8. The `Metadata` struct contains an additional `was_encrypted` field, which breaks the API, but should be easily resolvable. No known workarounds are available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"libsignal-service-rs doesn't sanity check plaintext envelopes are not sanity-checked","id":"CVE-2025-24904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL Injection endpoint 'get_codigobarras_cobranca.php' parameter 'codigo' in WeGIA","id":"CVE-2025-24905"},"packages":[],"prev":{"headline":"libsignal-service-rs Doesn't Check Origin of Sync Messages","id":"CVE-2025-24903"},"products":["libsignal-service-rs"],"published":"2025-02-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-02-13","vendors":["whisperfish"]},"summary":"Attackers can inject plaintext envelopes to bypass end-to-end encryption and authentication in Signal messaging clients using this library.","url":"https://insights.sbomify.com/CVE-2025-24904/"}