Skip to content

malformed proposed intoto entries can cause a panic

Moderate severity GitHub Reviewed Published May 26, 2023 in sigstore/rekor • Updated Nov 4, 2023

Package

gomod github.com/sigstore/rekor (Go)

Affected versions

< 1.2.0

Patched versions

1.2.0

Description

Impact

A malformed proposed entry of the intoto/v0.0.2 type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal.

Patches

This is fixed in v1.2.0 of Rekor.

Workarounds

No

References

Discovered by OSS-Fuzz

References

@bobcallaway bobcallaway published to sigstore/rekor May 26, 2023
Published to the GitHub Advisory Database May 26, 2023
Reviewed May 26, 2023
Published by the National Vulnerability Database May 26, 2023
Last updated Nov 4, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

0.078%
(35th percentile)

Weaknesses

CVE ID

CVE-2023-33199

GHSA ID

GHSA-frqx-jfcm-6jjr

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.