Is CVE-2022-4899 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-4899 being exploited in the wild.

How severe is CVE-2022-4899?

Low severity, with a CVSS score of 3.1, published 31 March 2023.

Which products and versions are affected?

zstd (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.4, ECOSYSTEM:introduced=0,fixed=1.5.4.0; github.com/facebook/zstd (Swift) SEMVER:introduced=0,fixed=1.5.4.

Is there a fix for CVE-2022-4899?

Yes. zstd (PyPI): upgrade to 1.5.4, 1.5.4.0 or later; github.com/facebook/zstd (Swift): upgrade to 1.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-4899?

Check whether you run zstd (PyPI) or github.com/facebook/zstd (Swift) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2022-4899: PYSEC-2023-121 - zstd vulnerable to buffer overrun

CVE-2022-4899 · Severity: low · CVSS 3.1 · Published 2023-03-31

zstd vulnerable to buffer overrun

Vendors: PyPI, Swift.

Quick answers

Is CVE-2022-4899 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2022-4899 being exploited in the wild.
How severe is CVE-2022-4899?: Low severity, with a CVSS score of 3.1, published 31 March 2023.
Which products and versions are affected?: zstd (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.4, ECOSYSTEM:introduced=0,fixed=1.5.4.0; github.com/facebook/zstd (Swift) SEMVER:introduced=0,fixed=1.5.4.
Is there a fix for CVE-2022-4899?: Yes. zstd (PyPI): upgrade to 1.5.4, 1.5.4.0 or later; github.com/facebook/zstd (Swift): upgrade to 1.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-4899?: Check whether you run zstd (PyPI) or github.com/facebook/zstd (Swift) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

zstd (PyPI): upgrade to 1.5.4, 1.5.4.0 or later
```
pip install "zstd>=1.5.4.0"
```
github.com/facebook/zstd (Swift): upgrade to 1.5.4 or later

Affected products

zstd (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.4, ECOSYSTEM:introduced=0,fixed=1.5.4.0
github.com/facebook/zstd (Swift) SEMVER:introduced=0,fixed=1.5.4

Identifiers

CVE-2022-4899
GHSA-5c9c-6x87-f9vm
PYSEC-2023-121

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.