Security readout for executives and security teams
Plain-English summary
Avahi-daemon used a predictable source port for wide-area DNS queries. That makes it easier for an attacker to inject false DNS responses, potentially causing systems to trust incorrect name-resolution data. The reported impact is limited integrity loss, not data theft or service outage.
Executive priority
Treat this as a moderate infrastructure hygiene issue. It is remotely reachable and unauthenticated in the CVSS model, but documented impact is limited to low integrity risk and no active exploitation is cited. Remediate through normal patch cycles, faster where Avahi is enabled in production.
Technical view
CVE-2024-52615 is a CWE-330 flaw in Avahi wide-area DNS handling. Red Hat describes fixed source ports for DNS queries, reducing randomness and simplifying malicious DNS response injection. CVSS 3.1 is 5.3 with network attack vector, no privileges, no user interaction, and low integrity impact.
Likely exposure
Most relevant exposure is Red Hat environments running affected avahi packages on RHEL 8, RHEL 9, RHEL 10, or RHCOS in OpenShift 4. RHEL 7 status is listed as unknown. Exposure depends on whether Avahi-daemon and wide-area DNS query behavior are present.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The weakness is easier DNS response injection because the source port is constant. Sources do not provide public exploit details, confirmed attacks, or affected non-Red Hat product versions beyond the listed records.
Researcher notes
The key validation question is whether Avahi-daemon performs wide-area DNS queries on the assessed host. Source evidence supports predictable source-port behavior and response-injection risk, but does not establish exploit prevalence, broader vendor impact, or universal exposure across all Avahi deployments.
Mitigation direction
- Apply vendor updates from the relevant Red Hat advisory.
- Prioritize affected RHEL and OpenShift nodes running avahi or rhcos packages.
- Check Red Hat CVE guidance for product-specific fixed versions.
- Review whether Avahi-daemon is required on exposed systems.
- Track upstream Avahi PR 577 for implementation context.
Validation and detection
- Inventory systems with installed avahi or rhcos packages.
- Compare installed package versions against Red Hat affected entries.
- Confirm RHSA-2025:11402 or RHSA-2025:16441 applicability.
- Verify vulnerability scanners no longer flag CVE-2024-52615 after updates.
- Document RHEL 7 findings separately because status is listed unknown.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-330: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-52615 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4redhatVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Reported to Red Hat.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2025:11402CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:16441CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2024-52615CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2326418CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/avahi/avahi/pull/577CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Insufficiently Random Values
Use of Insufficiently Random Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.