vciy

CVE-2020-25683

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A flaw was found in dnsmasq before version 2.83

CVE-2020-256834 of 4 sources documented this
47

rank 47 = 22 + 15 + 4 + 6 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.86041  ·  without this subject the record ranks 25

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.9, from NVD  ·  without this subject the record ranks 32

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-09-12  ·  without this subject the record ranks 43

How much of the world it touches

NVD CPE configurations

5 products in the CPE ranges  ·  without this subject the record ranks 41

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 47

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.63Mover the next 30 days, if this record is yours
Movement-$978,000on 2025-11-21, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$2.63M = $4.99M incident cost x 0.6121449559255632 exposure x 0.86041 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.86041EPSSNOT IN KEVas of 2026-09-20
Severity5.9 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
RISING10Risen from 0.0258 to 0.86041 across 32 observations. arc-rules@v1

Foresight · where to check next

FortinetCVE-2015-3113FortinetVMware vCenterFacebook WhatsAppAdobe Acrobat25683

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running dnsmasq? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · high attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-122 Heap-based Buffer Overflowreceipt
Published consequencesCWE-122: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Integrity, Confidentiality, Availability, Access Control: Execute…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchdnsmasq 2.83receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD5.9 MEDIUMreceipt
Exploit probability0.86041 · top 0.28% of all CVEsreceipt
Blast breadth3 products across 3 vendorsderived
Assigned byredhatreceipt
Recorded changes32 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productdnsmasqreceipt
Published rangesthekelleys dnsmasq < 2.83; fedoraproject fedora 32; fedoraproject fedora 33; debian linux 9.0receipt
Show all 5 published ranges
thekelleys dnsmasq < 2.83
fedoraproject fedora 32
fedoraproject fedora 33
debian linux 9.0
debian linux 10.0

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in dnsmasq when DNSSEC is enabled and before it validates the received DNS entries. A remote attacker, who can create valid DNS replies, could use this flaw to cause an overflow in a heap-allocated memory. This flaw is caused by the lack of length checks in rfc1035.c:extract_name(), which could be abused to make the code execute memcpy() with a negative size in get_rdata() and cause a crash in dnsmasq, resulting in a denial of service. The highest threat from this vulnerability is to system availability. receipt

NVD's analysis a second authority

severity
5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-122
affected versions
thekelleys dnsmasq < 2.83; fedoraproject fedora 32; fedoraproject fedora 33; and 2 more, listed in full below

check it yourself jsof-tech.com bugzilla.redhat.com lists.fedoraproject.org security.gentoo.org debian.org lists.fedoraproject.org +1 morereceipt

Dated events

2022-01-06EPSS moved 0.03 to 0.112026-06-15EPSS moved 0.31 to 0.86

Movement the material steps

14 Apr 20210.0258
6 Jan 20220.10619 · crossed 0.10
4 Feb 20220.21571
1 Apr 20220.01319 · crossed 0.10
7 Mar 20230.23975 · crossed 0.10 · scoring model v2023.03.01
8 Nov 20230.08665 · crossed 0.10
23 Feb 20240.11489 · crossed 0.10
23 Apr 20240.08454 · crossed 0.10
24 Nov 20240.11619 · crossed 0.10
11 Dec 20240.08553 · crossed 0.10
17 Mar 20250.28959 · crossed 0.10 · scoring model v2025.03.14
29 Mar 20250.04054 · crossed 0.10
30 Mar 20250.28959 · crossed 0.10
12 Sep 20250.57368 · crossed 0.50
29 Oct 20250.24767 · crossed 0.50
18 Nov 20250.63347 · crossed 0.50
21 Nov 20250.31317 · crossed 0.50
15 Jun 20260.86157 · crossed 0.50 · scoring model v2026.06.15
28 Jun 20260.86041

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 32 observations
14 Apr 20210.0258
6 Jan 20220.10619
4 Feb 20220.21571
1 Apr 20220.01319
7 Mar 20230.23975
1 Aug 20230.26355
27 Aug 20230.25098
6 Oct 20230.27701
8 Nov 20230.08665
23 Feb 20240.11489
23 Apr 20240.08454
9 Nov 20240.09897
24 Nov 20240.11619
11 Dec 20240.08553
17 Dec 20240.05805
27 Dec 20240.06562
17 Mar 20250.28959
29 Mar 20250.04054
30 Mar 20250.28959
15 Jun 20250.30243
12 Sep 20250.57368
1 Oct 20250.51239
27 Oct 20250.57368
28 Oct 20250.51239
29 Oct 20250.24767
5 Nov 20250.31317
18 Nov 20250.63347
21 Nov 20250.31317
27 Dec 20250.3738
28 Dec 20250.31317
15 Jun 20260.86157
28 Jun 20260.86041

32 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.86041Published2021-01-20Index as of2026-06-28

Exploit probability more than doubled between 2025-03-29 and 2025-03-30 (0.04054 → 0.28959) and the record had been public for 5 years, 5 months when this index was last written.

Published 2021-01-20 receipt · Index as of 2026-06-28 derived

The pattern, elsewhere

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-25249 · Fortinet FortiSwitchManagermatches 6 of 9KEV listed · 2026receipt
CVE-2015-3113matches 5 of 8KEV listed · 2015receipt
CVE-2023-27997 · Fortinet FortiOS-6K7Kmatches 5 of 9KEV listed · 2023receipt
CVE-2024-38812 · VMware vCenter Servermatches 5 of 9KEV listed · 2024receipt
CVE-2019-3568 · Facebook WhatsApp for Androidmatches 5 of 9KEV listed · 2019receipt
CVE-2021-21017 · Adobe Acrobat Readermatches 4 of 9KEV listed · 2021receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3216 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

dnsmasq

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2020-25683.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.