Open Bug 1612806 Opened 9 months ago Updated 8 months ago

Crash in [@ nssCKFWObject_GetAttribute | NSSCKFWC_GetAttributeValue | PK11_ReadAttribute]

Categories

(NSS :: Libraries, defect, P3)

Unspecified
macOS
defect

Tracking

(Not tracked)

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-d411acda-d94a-468c-8b67-946440200131.

Top 10 frames of crashing thread:

0 libnssckbi.dylib nssCKFWObject_GetAttribute security/nss/lib/ckfw/object.c:617
1 libnssckbi.dylib NSSCKFWC_GetAttributeValue security/nss/lib/ckfw/wrap.c:2280
2 libnss3.dylib PK11_ReadAttribute security/nss/lib/pk11wrap/pk11obj.c:120
3 libnss3.dylib PK11_FindRawCertsWithSubject security/nss/lib/pk11wrap/pk11obj.c:1971
4 XUL mozilla::psm::NSSCertDBTrustDomain::FindIssuer security/certverifier/NSSCertDBTrustDomain.cpp:260
5 XUL mozilla::pkix::BuildForward security/nss/lib/mozpkix/lib/pkixbuild.cpp:365
6 XUL mozilla::pkix::PathBuildingStep::Check security/nss/lib/mozpkix/lib/pkixbuild.cpp:211
7 XUL mozilla::psm::CheckCandidates security/certverifier/NSSCertDBTrustDomain.cpp:193
8 XUL mozilla::psm::NSSCertDBTrustDomain::FindIssuer security/certverifier/NSSCertDBTrustDomain.cpp:348
9 XUL mozilla::pkix::BuildForward security/nss/lib/mozpkix/lib/pkixbuild.cpp:365

macOS-only low-volume crasher. This doesn't seem like a new bug, the oldest buildid which has it is 20191202091209, that was when nightly was at version 72. The crash is a NULL-pointer dereference and the lower frames of the stack are always the same but I found at least two separate stacks leading to this issue.

Component: Security → Security: PSM
Assignee: nobody → nobody
Component: Security: PSM → Libraries
Product: Core → NSS
QA Contact: jjones
Version: unspecified → other

The priority flag is not set for this bug.
:jcj, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jjones)

Low-volume, non-obvious. We're going to watch it.

Flags: needinfo?(jjones)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.