Hide Forgot
+++ This bug was initially created as a clone of Bug #717338 +++ Description of problem: When my application attempts to load a private key file, it crashes in pem_CreateObject(). Version-Release number of selected component (if applicable): nss-3.12.10-4.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. SECMOD_LoadUserModule(libnsspem.so) 2. PK11_CreateGenericObject(CKA_CLASS=CKO_PRIVATE_KEY,CKA_TOKEN=CK_TRUE) Actual results: pem_CreateObject() passes an uninitialized certDER.data to nss_ZFreeIf() Additional info: When I cut it down to the bare minimum to try to create a simpler reproducer, I don't get a crash any more, but valgrind at least still flags the errors. --- Additional comment from nalin on 2011-06-28 11:24:30 EDT --- Created attachment 510308 [details] minimal attempt at a reproducer --- Additional comment from nalin on 2011-06-28 11:59:56 EDT --- Created attachment 510313 [details] patch for NSS which fixes my application --- Additional comment from emaldona on 2011-09-12 12:09:05 EDT --- Nalin, I'm picking up your patch. It will be applied with other I have in the queue. Thanks.
I was comparing the sources after all approved patches had been applied to RHEL 6.3 and Fedora and I noticed that we are missing this one. I recommend picking this up for RHEL 6.3.
Created attachment 571508 [details] Intialize the pointer to NULL This is Nalin' patch updated so it applies after all the other patches.
Elio, can you attack a pointer to the full pobject.c The given context is not enough to review the patch. Thanks.
Aha, looking at the bigger context I realized the patch needs a bit more work.
Created attachment 571565 [details] init pointer to NULL and also bail out if mem alloc fails
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No Documentation needed
Comment on attachment 571565 [details] init pointer to NULL and also bail out if mem alloc fails r+ relyea
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0973.html