Cockpit up to 2.2.1 authentication bypass

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.
8.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Cockpit up to 2.2.1. It has been classified as problematic. The affected element is an unknown function. Performing a manipulation results in authentication bypass. This vulnerability is identified as CVE-2022-2818. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Cockpit up to 2.2.1. It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository cockpit-hq/cockpit prior to 2.2.2.

The weakness was released 08/15/2022. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2022-2818 since 08/15/2022. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.2.2 eliminates this vulnerability. Applying the patch 4bee1b903ee20818f4a8ecb9d974b9536cc54cb4 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.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.6
VulDB Meta Temp Score: 8.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CNA Base Score: 9.8
CNA Vector (huntr.dev): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Authentication bypass
CWE: CWE-305 / CWE-287
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: Cockpit 2.2.2
Patch: 4bee1b903ee20818f4a8ecb9d974b9536cc54cb4

Timelineinfo

08/15/2022 🔍
08/15/2022 +0 days 🔍
08/15/2022 +0 days 🔍
02/25/2026 +1290 days 🔍

Sourcesinfo

Advisory: 4bee1b903ee20818f4a8ecb9d974b9536cc54cb4
Status: Confirmed

CVE: CVE-2022-2818 (🔍)
GCVE (CVE): GCVE-0-2022-2818
GCVE (VulDB): GCVE-100-206421

Entryinfo

Created: 08/15/2022 15:46
Updated: 02/25/2026 17:07
Changes: 08/15/2022 15:46 (50), 09/11/2022 14:24 (1), 09/11/2022 14:25 (11), 02/25/2026 17:07 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!