{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45193 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45193 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45193 is a medium-severity vulnerability in n/a, published on 22 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45193 and fix it if it is affected.\n\nWhat it is: CVE-2024-45193 is a medium-severity vulnerability in n/a, published on 22 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45193 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-45193/ (Markdown: https://insights.sbomify.com/CVE-2024-45193/index.md)","id":"CVE-2024-45193","markdown":"https://insights.sbomify.com/CVE-2024-45193/index.md","name":"CVE-2024-45193","record":{"aliases":["DEBIAN-CVE-2024-45193","ECHO-aabb-f88e-39bf","GHSA-w58g-789j-fj58","UBUNTU-CVE-2024-45193"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Matrix libolm library","requires_auth":"low_privilege","summary":"Attackers can exploit Ed25519 signature malleability in the libolm library due to missing validation, potentially bypassing security checks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"olm","vendor":"matrix"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"An issue was discovered in Matrix libolm through 3.2.16. There is Ed25519 signature malleability due to lack of validation criteria (does not ensure that S \u003c n). This refers to the libolm implementation of Olm. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.","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":"Weak cryptography in n/a","id":"CVE-2024-45193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-45194"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2024-45192"},"products":["n/a"],"published":"2024-08-22","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-34813","kev_date_added":null,"published":"2021-06-16"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2024-45191","kev_date_added":null,"published":"2024-08-22"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2024-45192","kev_date_added":null,"published":"2024-08-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-10","vendors":["n/a"]},"summary":"Attackers can exploit Ed25519 signature malleability in the libolm library due to missing validation, potentially bypassing security checks.","url":"https://insights.sbomify.com/CVE-2024-45193/"}