{"answers":{"affected":"3 open source packages ship an affected version, including matrix-synapse. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18835 in the wild and no public exploit code.","fix":"Upgrade matrix-synapse to 1.5.0 or later.","what":"CVE-2019-18835 is a critical vulnerability in n/a, published on 7 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18835 and fix it if it is affected.\n\nWhat it is: CVE-2019-18835 is a critical vulnerability in n/a, published on 7 Nov 2019. 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-2019-18835 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-synapse (PyPI): affected all versions; fixed in 1.5.0\n- matrix-synapse (PyPI): affected all versions; fixed in 1.5.0\n- matrix-synapse (PyPI): affected all versions; fixed in 1.5.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-2019-18835/ (Markdown: https://insights.sbomify.com/CVE-2019-18835/index.md)","id":"CVE-2019-18835","markdown":"https://insights.sbomify.com/CVE-2019-18835/index.md","name":"CVE-2019-18835","record":{"aliases":["GHSA-cppw-2mf8-qpm5","PYSEC-2019-186","UBUNTU-CVE-2019-18835"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Matrix Synapse server","requires_auth":"none","summary":"Attackers can bypass signature checks on federation APIs, allowing unsigned or spoofed events to be accepted by the Matrix Synapse server.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"synapse","vendor":"matrix"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Matrix Synapse before 1.5.0 mishandles signature checking on some federation APIs. Events sent over /send_join, /send_leave, and /invite may not be correctly signed, or may not come from the expected servers.","ecosystems":["PyPI"],"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":"Improper Verification of Cryptographic Signature in matrix-synapse","id":"CVE-2019-18835","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":3,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-18836"},"packages":[{"ecosystem":"PyPI","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"matrix-synapse","purl":null,"source":"GHSA-cppw-2mf8-qpm5"},{"ecosystem":"PyPI","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"matrix-synapse","purl":"pkg:pypi/matrix-synapse","source":"GHSA-cppw-2mf8-qpm5"},{"ecosystem":"PyPI","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"matrix-synapse","purl":"pkg:pypi/matrix-synapse","source":"PYSEC-2019-186"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-18834"},"products":["n/a"],"published":"2019-11-07","related":[{"cvss_score":8.7,"headline":"Synapse allows a a malformed invite to break the invitee's `/sync`","id":"CVE-2024-52815","kev_date_added":null,"published":"2024-12-03"},{"cvss_score":8.2,"headline":"Synapse allows unsupported content types to lead to memory exhaustion","id":"CVE-2024-52805","kev_date_added":null,"published":"2024-12-03"},{"cvss_score":8.2,"headline":"Synapse can be forced to thumbnail unexpected file formats, invoking external, potentially untrustworthy decoders","id":"CVE-2024-53863","kev_date_added":null,"published":"2024-12-03"},{"cvss_score":7.5,"headline":"Synapse denial of service through media disk space consumption","id":"CVE-2024-37302","kev_date_added":null,"published":"2024-12-03"},{"cvss_score":7.5,"headline":"Matrix Synapse Authorization Error","id":"CVE-2018-12423","kev_date_added":null,"published":"2018-06-14"},{"cvss_score":7.5,"headline":"Matrix Synapse Security Filtering Flaw","id":"CVE-2018-12291","kev_date_added":null,"published":"2018-06-13"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass signature checks on federation APIs, allowing unsigned or spoofed events to be accepted by the Matrix Synapse server.","url":"https://insights.sbomify.com/CVE-2019-18835/"}