matrix-android-sdk2 up to 1.5.0 Message key exchange without entity authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in matrix-android-sdk2 up to 1.5.0. The affected element is an unknown function of the component Message Handler. Such manipulation leads to key exchange without entity authentication. This vulnerability is uniquely identified as CVE-2022-39246. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in matrix-android-sdk2 up to 1.5.0 and classified as critical. Affected by this issue is an unknown code block of the component Message Handler. The manipulation with an unknown input leads to a key exchange without entity authentication vulnerability. Using CWE to declare the problem leads to CWE-322. The product performs a key exchange with an actor without verifying the identity of that actor. Impacted is integrity. CVE summarizes:

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)`.

The weakness was disclosed 09/29/2022 as GHSA-2pvj-p485-cp3m. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2022-39246 since 09/02/2022. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.5.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 77df720a238d17308deab83ecaa37f7a4740a17e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 6.0

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Key exchange without entity authentication
CWE: CWE-322 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: matrix-android-sdk2 1.5.1
Patch: 77df720a238d17308deab83ecaa37f7a4740a17e

Timelineinfo

09/02/2022 🔍
09/29/2022 +27 days 🔍
09/29/2022 +0 days 🔍
10/25/2022 +26 days 🔍

Sourcesinfo

Advisory: GHSA-2pvj-p485-cp3m
Status: Confirmed

CVE: CVE-2022-39246 (🔍)
GCVE (CVE): GCVE-0-2022-39246
GCVE (VulDB): GCVE-100-209732

Entryinfo

Created: 09/29/2022 08:30
Updated: 10/25/2022 08:31
Changes: 09/29/2022 08:30 (53), 10/25/2022 08:31 (11)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!