Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-93mf-426m-g6x9 | CoreDNS: DNS Cache Pinning via etcd Lease ID Confusion |
Fri, 12 Sep 2025 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Coredns.io
Coredns.io coredns |
|
| Vendors & Products |
Coredns.io
Coredns.io coredns |
Wed, 10 Sep 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 10 Sep 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 09 Sep 2025 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | CoreDNS is a DNS server that chains plugins. Starting in version 1.2.0 and prior to version 1.12.4, the CoreDNS etcd plugin contains a TTL confusion vulnerability where lease IDs are incorrectly used as TTL values, enabling DNS cache pinning attacks. This effectively creates a DoS condition for DNS resolution of affected services. The `TTL()` function in `plugin/etcd/etcd.go` incorrectly casts etcd lease IDs (64-bit integers) to uint32 and uses them as TTL values. Large lease IDs become very large TTLs when cast to uint32. This enables cache pinning attacks. Version 1.12.4 contains a fix for the issue. | |
| Title | CoreDNS: DNS Cache Pinning via etcd Lease ID Confusion | |
| Weaknesses | CWE-681 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-09-10T14:26:13.850Z
Reserved: 2025-08-22T14:30:32.222Z
Link: CVE-2025-58063
Updated: 2025-09-10T14:26:02.976Z
Status : Deferred
Published: 2025-09-09T20:15:48.057
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-58063
OpenCVE Enrichment
Updated: 2025-09-12T09:11:48Z
Github GHSA