vciy

CVE-2023-28753

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.

netconsd prior to v0.2 was vulnerable to an integer overflow in its parse_packet function

CVE-2023-287534 of 4 sources documented this
43

rank 43 = 15 + 25 + 1 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.01851  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 18

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-05-20  ·  without this subject the record ranks 42

How much of the world it touches

NVD CPE configurations

1 product 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 43

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$92,400over the next 30 days, if this record is yours
Movement+$303,000on 2026-05-20, the last material move, 26 days before this reading
Basisassumeda published average, not your estate

$92,400 = $4.99M incident cost x 1 exposure x 0.01851 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.01851EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00043 to 0.01851 across 25 observations. arc-rules@v1

Foresight · where to check next

Facebook WhatsAppCVE-2015-3113FortinetVMware vCenterFortinetAdobe Acrobat28753

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

Sources disagree here.

Weakness class
FacebookCWE-122: Heap-based Buffer Overflowreceipt
NVDCWE-787receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Facebook netconsd? 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 · low attack complexityreceipt
ImpactComplete confidentiality, integrity and 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.

Fixed in0.2receipt
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: Proof-of-concept published · 1 public repository, 2024-09-12.

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

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.01851 · top 22% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byfacebookreceipt
Recorded changes28 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productFacebook netconsdreceipt
Published rangesfacebook netconsd 0.1receipt
Fixed in0.2receipt

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

netconsd prior to v0.2 was vulnerable to an integer overflow in its parse_packet function. A malicious individual could leverage this overflow to create heap memory corruption with attacker controlled data. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-787
affected versions
facebook netconsd 0.1
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The CNA and NVD map this to different weakness classes. Both are shown because both were published; we do not pick one.

check it yourself facebook.com github.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.182025-03-19EPSS moved 0.18 to 0.462026-06-15EPSS moved 0.18 to 0.02

Movement the material steps

19 May 20230.00043
17 Mar 20250.18376 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.46164
20 Mar 20250.18376
27 Mar 20250.46164
28 Mar 20250.18376
29 Mar 20250.46164
30 Mar 20250.18376
15 Apr 20250.09312 · crossed 0.10
18 Nov 20250.18376 · crossed 0.10
21 Nov 20250.06815 · crossed 0.10
20 May 20260.14206 · crossed 0.10
15 Jun 20260.01851 · crossed 0.10 · scoring model v2026.06.15

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

Show all 25 observations
19 May 20230.00043
27 May 20230.00084
17 Apr 20240.00116
24 May 20240.00218
19 Jun 20240.00245
28 Oct 20240.00281
8 Dec 20240.00290
17 Dec 20240.00412
17 Mar 20250.18376
19 Mar 20250.46164
20 Mar 20250.18376
27 Mar 20250.46164
28 Mar 20250.18376
29 Mar 20250.46164
30 Mar 20250.18376
15 Apr 20250.09312
22 Oct 20250.08976
24 Oct 20250.06815
18 Nov 20250.18376
21 Nov 20250.06815
10 Feb 20260.07677
14 Mar 20260.08137
20 May 20260.14206
4 Jun 20260.1754
15 Jun 20260.01851

25 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.01851Published2023-05-18Public PoC2024-09-12Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.18376 → 0.46164) and the record had been public for 3 years when this index was last written.

Published 2023-05-18 receipt · Public PoC 2024-09-12 receipt · Index as of 2026-06-15 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-2019-3568 · Facebook WhatsApp for Androidmatches 10 of 10KEV listed · 2019receipt
CVE-2015-3113matches 9 of 9KEV listed · 2015receipt
CVE-2023-27997 · Fortinet FortiOS-6K7Kmatches 9 of 10KEV listed · 2023receipt
CVE-2024-38812 · VMware vCenter Servermatches 9 of 10KEV listed · 2024receipt
CVE-2025-25249 · Fortinet FortiSwitchManagermatches 8 of 10KEV listed · 2026receipt
CVE-2021-21017 · Adobe Acrobat Readermatches 8 of 10KEV 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

Browse the index from here

These are index-wide views, not findings about CVE-2023-28753.

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.