{"vuid":"VU#336446","idnumber":"336446","name":"OpenCA libCheckSignature function fails to properly verify the signature of certificates","keywords":["OpenCA","libCheckSignature","crypto-utils.lib","signature certificate","certificate database"],"overview":"OpenCA may accept a signature from a certificate if the certificate's chain is trusted by the chain directory of OpenCA.","clean_desc":"The OpenCA PKI Development Project is a Certification Authority. A vulnerability exists in the way the libCheckSignature function compares the certificate in the database and the certificate of the signer. From the OpenCA Security Advisory: The comparison of the certificate in the database and the certificate of the signer was only performed on base of the serial of the certificate. The design of the function can cause the acceptance\nof a signature if the chain of the signature can create a trust relationship to the chain directory of OpenCA and a certificate with a matching serial exists in the used PKI. See the OpenCA Security Advisory for further details.","impact":"OpenCA may accept the signature of a certificate if the certificate's chain is trusted by the chain directory of OpenCA. This could allow a certificate from another PKI to authorize operations on the used PKI.","resolution":"Upgrade\nOpenCA version 0.9.1.7 has been released to address this vulnerability. Apply Patch\nOpenCA has supplied a patch which resolves this issue.","workarounds":"","sysaffected":"","thanks":"Thanks to \nOpenCA\n for the information contained in their security advisory. OpenCA credits Alexandru Matei for discovering this vulnerability.","author":"This document was written by Damon Morda.","public":["http://www.openca.org/","http://www.openca.org/news/CAN-2004-0004.txt","http://www.secunia.com/advisories/10664/"],"cveids":["CVE-2004-0004"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-01-16T20:01:35Z","publicdate":"2004-01-16T00:00:00Z","datefirstpublished":"2004-01-19T16:59:19Z","dateupdated":"2004-01-22T18:45:25Z","revision":16,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"10","cam_population":"10","cam_impact":"2","cam_easeofexploitation":"9","cam_attackeraccessrequired":"20","cam_scorecurrent":"1.6875","cam_scorecurrentwidelyknown":"2.025","cam_scorecurrentwidelyknownexploited":"3.375","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":1.6875,"vulnote":null}