Skip to content

zstd vulnerable to buffer overrun

High severity GitHub Reviewed Published Mar 31, 2023 to the GitHub Advisory Database • Updated Sep 20, 2023

Package

swift github.com/facebook/zstd (Swift)

Affected versions

< 1.5.4

Patched versions

1.5.4
pip zstd (pip)
< 1.5.4.0
1.5.4.0

Description

A vulnerability was found in zstd v1.4.10, where an attacker can supply an empty string as an argument to the command line tool to cause buffer overrun.

References

Published by the National Vulnerability Database Mar 31, 2023
Published to the GitHub Advisory Database Mar 31, 2023
Reviewed Jun 6, 2023
Last updated Sep 20, 2023

Severity

High

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
High

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:H

EPSS score

0.212%
(60th percentile)

Weaknesses

CVE ID

CVE-2022-4899

GHSA ID

GHSA-5c9c-6x87-f9vm

Source code

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