Closed
Bug 628114
Opened 14 years ago
Closed 14 years ago
crash in ckcapi_mdObject_Destroy when trying to delete a certificate
Categories
(NSS :: Libraries, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.13
People
(Reporter: mmahkamov, Assigned: mmahkamov)
Details
(Keywords: crash)
Attachments
(1 file)
377 bytes,
patch
|
wtc
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.7.62 Version/11.01
Build Identifier: NSS 3.12.8
To delete a certificate from the Microsoft CAPI store, ckcapi_mdObject_Destroy does the following:
1. CertFindCertificateInStore to get the certificate context
2. Call CertDeleteCertificateFromStore to delete the certificate from MS CAPI store
3. Redundant call to CertFreeCertificateContext which leads to a crash
Reproducible: Always
Steps to Reproduce:
1. call SEC_DeletePermCertificate, pass any certificate from Microsoft CAPI store as an argument.
Actual Results:
The application crashes with an access violation reading invalid memory address
Expected Results:
The certificate is successfully deleted or an error code is returned
MSDN says CertDeleteCertificateFromStore always calls CertFreeCertificateContext. Removing the call to CertFreeCertificateContext solves the problem.
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #506221 -
Flags: review?(nelson)
Updated•14 years ago
|
Attachment #506221 -
Flags: review?(nelson) → review?(rrelyea)
Comment 2•14 years ago
|
||
Comment on attachment 506221 [details] [diff] [review]
patch to ckcapi_mdObject_Destroy
r=wtc. Thanks for the patch.
Attachment #506221 -
Flags: review?(rrelyea) → review+
Updated•14 years ago
|
Assignee: nobody → wtc
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P2
Target Milestone: --- → 3.13
Updated•14 years ago
|
Assignee: wtc → mmahkamov
Comment 3•14 years ago
|
||
Patch checked in on the NSS trunk (NSS 3.13).
Checking in cobject.c;
/cvsroot/mozilla/security/nss/lib/ckfw/capi/cobject.c,v <-- cobject.c
new revision: 1.7; previous revision: 1.6
done
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•