Resource Leak Affecting bpftool-debuginfo package, versions <0:6.1.106-116.188.amzn2023


Severity

Recommended
medium

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.04% (6th 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-AMZN2023-BPFTOOLDEBUGINFO-7897354
  • published5 Sept 2024
  • disclosed21 Aug 2024

Introduced: 21 Aug 2024

CVE-2024-43873  (opens in a new tab)
CWE-402  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 bpftool-debuginfo to version 0:6.1.106-116.188.amzn2023 or higher.
This issue was patched in ALAS2023-2024-709.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bpftool-debuginfo package and not the bpftool-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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

vhost/vsock: always initialize seqpacket_allow

There are two issues around seqpacket_allow:

  1. seqpacket_allow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized.
  2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared, then seqpacket_allow will not be cleared appropriately (existing apps I know about don't usually do this but it's legal and there's no way to be sure no one relies on this).

To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features

CVSS Scores

version 3.1