sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sigstore | sigstore-js | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sigstore | Sigstore |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-52v5-jr5w-gjxr | sigstore's `certificateOIDs` verification constraints are silently dropped and never enforced |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.173% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sigstore
Sigstore sigstore |
|
| Vendors & Products |
Sigstore
Sigstore sigstore |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 4.1.1, the documented certificateOIDs option in sigstore.verify() is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked and applications relying on certificateOIDs to restrict which certificates may sign artifacts can accept unauthorized certificates. This issue is fixed in version 4.1.1. | |
| Title | sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|