CVE-2008-5082: Medium severity red hat certificate system vulnerability
During the internal code review, it was discovered that Red Hat Certificate System / Dogtag Certificate System does not properly verify challenge response received during the enrollment of new security token.
If keys are generated on the token during the enrollment, TPS correctly verifies that the requestor possesses the private key, but fails to verify that the key really exists on the token and is not only in software.
An attacker with access to blank token known to TPS component and with privilege to perform enrollments of new tokens could use this flaw to successfully finish enrollment procedure with the software generated key instead of the one stored in the token.
Affected versions: Red Hat Certificate System 7.1, 7.2, 7.3 Dogtag Certificate System 1.0
Other sources
The verifyProof function in the Token Processing System (TPS) component in Red Hat Certificate System (RHCS) 7.1 through 7.3 and Dogtag Certificate System 1.0 returns successfully even when token enrollment did not use the hardware key, which allows remote authenticated users with enrollment privileges to bypass intended authentication policies by performing enrollment with a software key.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2008-5082?
CVE-2008-5082 has been assigned a moderate severity level due to the risk of improper authentication during the enrollment of security tokens.
How do I fix CVE-2008-5082?
To mitigate CVE-2008-5082, you should apply the latest updates provided by Red Hat for the affected versions of the Dogtag Certificate System and Red Hat Certificate System.
Who is affected by CVE-2008-5082?
CVE-2008-5082 affects users of Red Hat Certificate System versions 7.1, 7.2, 7.3 and Dogtag Certificate System version 1.0.
What impact does CVE-2008-5082 have on security?
CVE-2008-5082 could potentially allow unauthorized users to enroll for security tokens without proper challenge-response verification.
Is there a workaround for CVE-2008-5082?
Currently, there is no known workaround for CVE-2008-5082 other than applying the recommended security updates.