CVE Tools

CVE-2022-2837

CVE-2022-2837 is an open redirect in coreDNS (CVSS 6.1, Medium).

No known exploitation. EPSS puts it in the 34th percentile. Only a workaround so far.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, GitHub

What to do

No fixed build is published yet. The vendor describes a workaround.

  • n/a coreDNSAffected: unknownUpgrade to: not statedStated by: CVE record
  • Go github.com/coredns/corednsAffected: ≤ 1.9.3Upgrade to: after 1.9.3Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

A flaw was found in coreDNS. This flaw allows a malicious user to redirect traffic intended for external top-level domains (TLD) to a pod they control by creating projects and namespaces that match the TLD.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS34th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 34th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 735 days, from the signal feeds we watch.

  1. Workaround availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Scored 6.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2022-2837

Is CVE-2022-2837 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.4%.
Which versions are affected by CVE-2022-2837?
coreDNS: unknown. Github.com/coredns/coredns: ≤ 1.9.3.
How do I fix or mitigate CVE-2022-2837?
No fixed build is published yet. The vendor describes a workaround; apply it and watch for a patch.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for coreDNS, not every advisory.