CVE-2021-3502: A flaw was found in avahi 0.8-5.
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: avahi (AlmaLinux:9) 0.8-15.el9; avahi-compat-howl (AlmaLinux:9) 0.8-15.el9; avahi-compat-howl-devel (AlmaLinux:9) 0.8-15.el9.
Low priority for now. Upgrade to avahi (AlmaLinux:9) 0.8-15.el9; avahi-compat-howl (AlmaLinux:9) 0.8-15.el9; avahi-compat-howl-devel (AlmaLinux:9) 0.8-15.el9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 7, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-617
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| avahi | avahi | cpe:2.3:a:avahi:avahi |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- avahi avahi0.8-5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a avahi
- 0.8-5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | avahi | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-compat-howl | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-compat-howl-devel | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-compat-libdns_sd | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-compat-libdns_sd-devel | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-devel | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-glib | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-glib-devel | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-libs | before 0.8-15.el9 | 0.8-15.el9 |
| AlmaLinux:9 | avahi-tools | before 0.8-15.el9 | 0.8-15.el9 |
| Alpine:v3.18 | avahi | before 0.8-r5 | 0.8-r5 |
| Debian:12 | avahi | before 0.8-6 | 0.8-6 |
| openSUSE:Tumbleweed | avahi | before 0.8-7.2 | 0.8-7.2 |
| Red Hat:enterprise_linux:9::appstream | avahi-autoipd-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-compat-howl-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-compat-libdns_sd-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-debugsource | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-dnsconfd-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-glib | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-glib-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-gobject-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-libs-debuginfo | before 0:0.8-15.el9 | 0:0.8-15.el9 |
| Red Hat:enterprise_linux:9::appstream | avahi-tools | before 0:0.8-15.el9 | 0:0.8-15.el9 |
+12
Same product
avahi: all recordsOther highest-scoring records for the same primary product.
- CVE-2008-5081The originates_from_local_legacy_unicast_socket function (avahi-core/server.c) in avahi-daemon in Avahi before 0.6.24 allows remote attacker40Plan
- CVE-2017-6519avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, whic37Monitor
- CVE-2021-26720avahi-daemon-check-dns.sh in the Debian avahi package through 0.8-4 is executed as root via /etc/network/if-up.d/avahi-daemon, and allows a 31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2010-2244Jul 8, 2010 · The AvahiDnsPacket function in avahi-core/socket.c in avahi-daemon in Avahi 0.6.16 and 0.6.25 allows remote attackers to cause a denial of s18Monitor
- ← EarlierCVE-2011-1002Feb 22, 2011 · avahi-core/socket.c in avahi-daemon in Avahi before 0.6.29 allows remote attackers to cause a denial of service (infinite loop) via an empty29Monitor
- Later →CVE-2021-3468Jun 2, 2021 · A flaw was found in avahi in versions 0.6 up to 0.8.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:avahi | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-compat-howl | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-compat-howl-devel | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-compat-libdns_sd | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-compat-libdns_sd-devel | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-devel | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-glib | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-glib-devel | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-libs | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:avahi-tools | 0.8-15.el9 · AlmaLinux:9 | Package registry (OSV) |
| alpine:avahi | 0.8-r5 · Alpine:v3.18 | Package registry (OSV) |
| debian:avahi | 0.8-6 · Debian:12 | Package registry (OSV) |
| opensuse:avahi | 0.8-7.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:avahi-autoipd-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-compat-howl-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-compat-libdns_sd-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-debugsource | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-dnsconfd-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-glib | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-glib-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-gobject-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-libs-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-tools | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:avahi-tools-debuginfo | 0:0.8-15.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →