# CVE-2022-39246: matrix-android-sdk2 vulnerable to impersonation via forwarded Megolm sessions > Attackers can impersonate users by exploiting permissive key forwarding, allowing them to send messages appearing to come from others. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Sep 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-2pvj-p485-cp3m ## What is CVE-2022-39246? CVE-2022-39246 is a high-severity authentication bypass vulnerability in matrix-org matrix-android-sdk2, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 appearing to have come from another person. Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This attack is possible due to the key forwarding strategy implemented in the matrix-android-sdk2 that is too permissive. Starting with version 1.5.1, the default policy for accepting key forwards has been made more strict in the matrix-android-sdk2. The matrix-android-sdk2 will now only accept forwarded keys in response to previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the decrypted message upon decryption, based on whether the key used to decrypt the message was received from a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are decorated appropriately (for example, by showing a warning for such messages). As a workaroubnd, current users of the SDK can disable key forwarding in their forks using `CryptoService#enableKeyGossiping(enable: Boolean)`. Weakness: CWE-322 (Key Exchange without Entity Authentication), CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2022-39246? 2 open source packages ship an affected version, including org.matrix.android:matrix-android-sdk2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.matrix.android:matrix-android-sdk2` | Maven | All versions | 1.5.1 | | `org.matrix.android:matrix-android-sdk2` | Maven | All versions | 1.5.1 | Products: Matrix Software Development Kit. ## How do I fix CVE-2022-39246? Upgrade org.matrix.android:matrix-android-sdk2 to 1.5.1 or later. ## Is CVE-2022-39246 being exploited? There is no known exploitation of CVE-2022-39246 in the wild and no public exploit code. ## Other vulnerabilities in matrix-org matrix-android-sdk2 - [CVE-2022-39248](https://insights.sbomify.com/CVE-2022-39248/): matrix-android-sdk2 vulnerable to Olm/Megolm protocol confusion (high 8.6) - [CVE-2022-39255](https://insights.sbomify.com/CVE-2022-39255/): Matrix iOS SDK vulnerable ton Olm/Megolm protocol confusion (high 8.6) - [CVE-2022-39257](https://insights.sbomify.com/CVE-2022-39257/): Matrix iOS SDK vulnerable to impersonation via forwarded Megolm sessions (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-39246 and fix it if it is affected. What it is: CVE-2022-39246 is a high-severity authentication bypass vulnerability in matrix-org matrix-android-sdk2, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-39246 in the wild and no public exploit code. Affected packages and fixed versions: - org.matrix.android:matrix-android-sdk2 (Maven): affected all versions; fixed in 1.5.1 - org.matrix.android:matrix-android-sdk2 (Maven): affected all versions; fixed in 1.5.1 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-39246/ (Markdown: https://insights.sbomify.com/CVE-2022-39246/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39246 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39246 - OSV: https://osv.dev/vulnerability/CVE-2022-39246 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-39246/ Summaries are generated and may contain mistakes; the official description above is the record.