{"answers":{"affected":"2 open source packages ship an affected version, including org.matrix.android:matrix-android-sdk2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39248 in the wild and no public exploit code.","fix":"Upgrade org.matrix.android:matrix-android-sdk2 to 1.5.1 or later.","what":"CVE-2022-39248 is a high-severity vulnerability in matrix-org matrix-android-sdk2, published on 28 Sep 2022."},"fix_prompt":"Check this codebase for CVE-2022-39248 and fix it if it is affected.\n\nWhat it is: CVE-2022-39248 is a high-severity vulnerability in matrix-org matrix-android-sdk2, published on 28 Sep 2022. \nExploitation: There is no known exploitation of CVE-2022-39248 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.matrix.android:matrix-android-sdk2 (Maven): affected all versions; fixed in 1.5.1\n- org.matrix.android:matrix-android-sdk2 (Maven): affected all versions; fixed in 1.5.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-2022-39248/ (Markdown: https://insights.sbomify.com/CVE-2022-39248/index.md)","id":"CVE-2022-39248","markdown":"https://insights.sbomify.com/CVE-2022-39248/index.md","name":"CVE-2022-39248","record":{"aliases":["GHSA-fpgf-pjjv-2qgm"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"software_development_kit","vendor":"matrix"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-322","name":"Key Exchange without Entity Authentication"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"matrix-android-sdk2 is the Matrix SDK for Android. Prior to version 1.5.1, an attacker cooperating with a malicious homeserver can construct messages that legitimately appear to have come from another person, without any indication such as a grey shield. Additionally, a sophisticated attacker cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in order to send fake to-device messages appearing to originate from another user. This can allow, for example, to inject the key backup secret during a self-verification, to make a targeted device start using a malicious key backup spoofed by the homeserver. matrix-android-sdk2 would then additionally sign such a key backup with its device key, spilling trust over to other devices trusting the matrix-android-sdk2 device. These attacks are possible due to a protocol confusion vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. matrix-android-sdk2 version 1.5.1 has been modified to only accept Olm-encrypted to-device messages and to stop signing backups on a successful decryption. Out of caution, several other checks have been audited or added. This attack requires coordination between a malicious home server and an attacker, so those who trust their home servers do not need a workaround.","ecosystems":["Maven"],"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-android-sdk2 vulnerable to Olm/Megolm protocol confusion","id":"CVE-2022-39248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":null,"year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Matrix Javascript SDK vulnerable to impersonation via forwarded Megolm sessions","id":"CVE-2022-39249"},"packages":[{"ecosystem":"Maven","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"org.matrix.android:matrix-android-sdk2","purl":null,"source":"GHSA-fpgf-pjjv-2qgm"},{"ecosystem":"Maven","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"org.matrix.android:matrix-android-sdk2","purl":"pkg:maven/org.matrix.android/matrix-android-sdk2","source":"GHSA-fpgf-pjjv-2qgm"}],"prev":{"headline":"matrix-android-sdk2 vulnerable to impersonation via forwarded Megolm sessions","id":"CVE-2022-39246"},"products":["matrix-android-sdk2"],"published":"2022-09-28","related":[{"cvss_score":8.6,"headline":"Matrix iOS SDK vulnerable ton Olm/Megolm protocol confusion","id":"CVE-2022-39255","kev_date_added":null,"published":"2022-09-28"},{"cvss_score":7.5,"headline":"matrix-android-sdk2 vulnerable to impersonation via forwarded Megolm sessions","id":"CVE-2022-39246","kev_date_added":null,"published":"2022-09-28"},{"cvss_score":7.5,"headline":"Matrix iOS SDK vulnerable to impersonation via forwarded Megolm sessions","id":"CVE-2022-39257","kev_date_added":null,"published":"2022-09-28"}],"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":"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":"2025-04-23","vendors":["matrix-org"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2022-39248/"}