Incorrect Check of Function Return Value Affecting python3-perf package, versions <0:4.18.0-372.118.1.el8_6


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-PYTHON3PERF-7683912
  • published14 Aug 2024
  • disclosed16 Jul 2024

Introduced: 16 Jul 2024

CVE-2022-48829  (opens in a new tab)
CWE-253  (opens in a new tab)

How to fix?

Upgrade RHEL:8 python3-perf to version 0:4.18.0-372.118.1.el8_6 or higher.
This issue was patched in RHSA-2024:5281.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3-perf package and not the python3-perf package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes

iattr::ia_size is a loff_t, so these NFSv3 procedures must be careful to deal with incoming client size values that are larger than s64_max without corrupting the value.

Silently capping the value results in storing a different value than the client passed in which is unexpected behavior, so remove the min_t() check in decode_sattr3().

Note that RFC 1813 permits only the WRITE procedure to return NFS3ERR_FBIG. We believe that NFSv3 reference implementations also return NFS3ERR_FBIG when ia_size is too large.

CVSS Scores

version 3.1