# ALEA-2022:0359: tcpdump bug fix and enhancement update

> This update provides bug fixes and enhancements for tcpdump in AlmaLinux 8, improving network traffic monitoring capabilities.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2022

## What is ALEA-2022:0359?

ALEA-2022:0359 is a vulnerability in tcpdump, published on 1 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The tcpdump packages contain the tcpdump utility for monitoring network
traffic. The tcpdump utility can capture and display the packet headers on
a particular network interface or on all interfaces.

Bug Fix(es) and Enhancement(s):

* [RFE] tcpdump support for direction and interface needed in AlmaLinux8
(BZ#2037713)

## Which versions are affected by ALEA-2022:0359?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tcpdump` | AlmaLinux:8 | All versions | 14:4.9.3-2.el8_5.1 |

## How do I fix ALEA-2022:0359?

Upgrade to a fixed version.

## Is ALEA-2022:0359 being exploited?

There is no known exploitation of ALEA-2022:0359 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2022:0359 and fix it if it is affected.

What it is: ALEA-2022:0359 is a vulnerability in tcpdump, published on 1 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of ALEA-2022:0359 in the wild and no public exploit code.

Affected product: tcpdump. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALEA-2022-0359/ (Markdown: https://insights.sbomify.com/ALEA-2022-0359/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2022:0359

---
From sbomify Insights: https://insights.sbomify.com/ALEA-2022-0359/
Summaries are generated and may contain mistakes; the official description above is the record.