CVE-2022-2818: Cockpit Content Platform vulnerable to 2FA bypass
Cockpit Content Platform through version 2.2.1 is vulnerable to a two-factor authentication (2FA) bypass. The 2FA secret is disclosed in a JWT token after user logs into their account, allowing an attacker to bypass the 2FA code. A patch is available on the develop branch and is expected to be part of version 2.2.2.
Other sources
Cockpit Content Platform vulnerable to 2FA bypass
— Packagist
Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository cockpit-hq/cockpit prior to 2.2.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/cockpit-hq/cockpitto a version that resolves this vulnerability.Fixed in 2.2.2 - Upgrade
Upgrade
Cockpit Content Platformto a version that resolves this vulnerability.Fixed in 2.2.2
Event History
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-2818.
What is the severity of CVE-2022-2818?
The severity of CVE-2022-2818 is critical with a severity value of 8.8.
Which software versions are affected by CVE-2022-2818?
Cockpit Content Platform versions up to and including 2.2.1 and Agentejo Cockpit versions up to and exclusive 2.2.2 are affected by CVE-2022-2818.
How can an attacker exploit this vulnerability?
An attacker can exploit CVE-2022-2818 by bypassing two-factor authentication (2FA) through the disclosure of the 2FA secret in a JWT token after the user logs into their account.
Is there a patch available for CVE-2022-2818?
Yes, a patch is available on the `develop` branch of the Cockpit repository.