Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · denial of service

cve-program · severity unknownEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 7.5 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/coredns/coredns 1.11.0osv · severity unknownFixed by github.com/coredns/coredns 1.11.0KEV status unknown

cve-program · CVE-2023-28452

Published

An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal resolution. In an exploit, the attacker could just forge a response targeting the source port of a vulnerable resolver without the need to guess the correct TXID.

Read the publisher's advisory

euvd · EUVD-2024-2811

Published

An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal resolution. In an exploit, the attacker could just forge a response targeting the source port of a vulnerable resolver without the need to guess the correct TXID.

Read the publisher's advisory

nvd · CVE-2023-28452

Published

An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal resolution. In an exploit, the attacker could just forge a response targeting the source port of a vulnerable resolver without the need to guess the correct TXID.

Read the publisher's advisory

osv · GHSA-hfmw-7g3m-gj6q

Published

An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal resolution. In an exploit, the attacker could just forge a response targeting the source port of a vulnerable resolver without the need to guess the correct TXID.

Read the publisher's advisory

osv · GO-2024-3130

Published

CoreDNS vulnerable to TuDoor Attacks in github.com/coredns/coredns

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-28452

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "n/a",
                    "product": "n/a",
                    "versions": [
                        {
                            "version": "n/a",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-2811

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 18, 2024, 12:00:00 AM

dateUpdated: Mar 19, 2025, 8:44:07 PM

2 related source bulletins · separate from aliases

WID-SEC-W-2024-2177: CoreDNS: Mehrere Schwachstellen

CVE-2023-28452 · CVE-2023-30464

openSUSE-SU-2024:0319-1: Security update for coredns

CVE-2022-27191 · CVE-2022-28948 · CVE-2023-28452 · CVE-2023-30464 · CVE-2024-0874 · CVE-2024-22189

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-28452

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: NVD-CWE-noinfo · CWE-290

Original publisher date fields

published: 2024-09-18T15:15:13.957

lastModified: 2026-06-17T05:47:46.137

1 source CPE criteria · context only
  • cpe:2.3:a:coredns.io:coredns:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-hfmw-7g3m-gj6q

Published

github.com/coredns/coredns

Go

SEMVER · introduced 0 → fixed 1.11.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-3130

Published

github.com/coredns/coredns

Go

SEMVER · introduced 0 → fixed 1.11.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current