Jitsi 2.10.5550 HTTP Request clickjacking ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jitsi 2.10.5550. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component HTTP Request Handler. Performing a manipulation results in clickjacking. This vulnerability is identified as CVE-2022-36736. The attack can be initiated remotely. There is not any exploit available. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability was found in Jitsi 2.10.5550. It has been classified as problematic. This affects an unknown function of the component HTTP Request Handler. The manipulation with an unknown input leads to a clickjacking vulnerability. CWE is classifying the issue as CWE-451. The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks. This is going to have an impact on integrity. The summary by CVE is:
Jitsi-2.10.5550 was discovered to contain a vulnerability in its web UI which allows attackers to perform a clickjacking attack via a crafted HTTP request.
The weakness was released 09/08/2022. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-36736 since 07/25/2022. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1566.003 according to MITRE ATT&CK.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: ClickjackingCWE: CWE-451
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/25/2022 🔍09/08/2022 🔍
09/08/2022 🔍
04/30/2025 🔍
Sources
Advisory: github.comStatus: Not defined
Disputed: 🔍
CVE: CVE-2022-36736 (🔍)
GCVE (CVE): GCVE-0-2022-36736
GCVE (VulDB): GCVE-100-208131
Entry
Created: 09/08/2022 18:08Updated: 04/30/2025 00:05
Changes: 09/08/2022 18:08 (37), 10/14/2022 14:38 (11), 08/03/2024 14:48 (17), 04/30/2025 00:05 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.