Gitpod prior 2022.11.2.16 missing origin validation in websockets
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Gitpod. It has been classified as problematic. This vulnerability affects unknown code. The manipulation leads to missing origin validation in websockets. This vulnerability is traded as CVE-2023-0957. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Gitpod and classified as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a missing origin validation in websockets vulnerability. Using CWE to declare the problem leads to CWE-1385. The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Gitpod versions prior to release-2022.11.2.16. There is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability that allows attackers to make WebSocket connections to the Gitpod JSONRPC server using a victim’s credentials, because the Origin header is not restricted. This can lead to the extraction of data from workspaces, to a full takeover of the workspace.
The weakness was shared 03/03/2023. The advisory is shared at snyk.io. The identification of this vulnerability is CVE-2023-0957 since 02/22/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2022.11.2.16 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 12956988eec0031f42ffdfa3bdc3359f65628f9f 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.6
NVD Vector: 🔍
CNA Base Score: 8.2
CNA Vector (Snyk): 🔍
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: Missing origin validation in websocketsCWE: CWE-1385 / CWE-346 / CWE-345
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Gitpod 2022.11.2.16
Patch: 12956988eec0031f42ffdfa3bdc3359f65628f9f
Timeline
02/22/2023 🔍03/03/2023 🔍
03/03/2023 🔍
03/31/2023 🔍
Sources
Advisory: 12956988eec0031f42ffdfa3bdc3359f65628f9fStatus: Confirmed
CVE: CVE-2023-0957 (🔍)
GCVE (CVE): GCVE-0-2023-0957
GCVE (VulDB): GCVE-100-222269
Entry
Created: 03/03/2023 10:35Updated: 03/31/2023 08:40
Changes: 03/03/2023 10:35 (50), 03/31/2023 08:37 (1), 03/31/2023 08:40 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.