vciy

CVE-2023-45232

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.

Infinite loop in EDK II Network Package

CVE-2023-452324 of 4 sources documented this
22

rank 22 = 1 + 19 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.02101  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 3

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 22

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$64,200over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$64,200 = $4.99M incident cost x 0.6121449559255632 exposure x 0.02101 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.02101EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2024-01-24, 903 days at 0.02, as of 2026-07-15. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running TianoCore edk2? 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 availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')receipt
Published consequencesCWE-835: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 15 Jul 2026.
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, the CNA7.5 HIGHreceipt
CVSS, NVD7.5 HIGHreceipt
Exploit probability0.02101 · top 19% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byTianoCorereceipt
Recorded changes42 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productTianoCore edk2receipt
Published rangestianocore edk2 <= 202311receipt

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.

Attack path

Unauthenticated network requestno credentials, no interactionTianoCore edk2CWE-835 weaknessAvailability lossA:Hexploits CWE-835data compromise

What it is stated by the CNA

EDK2's Network Package is susceptible to an infinite loop vulnerability when parsing unknown options in the Destination Options header of IPv6. This vulnerability can be exploited by an attacker to gain unauthorized access and potentially lead to a loss of Availability. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-835
affected versions
tianocore edk2 <= 202311
also scored by
[email protected] 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself github.com openwall.com packetstormsecurity.com security.netapp.com lists.fedoraproject.org receipt

Movement the material steps

24 Jan 20240.00103
17 Mar 20250.01323 · scoring model v2025.03.14
15 Jun 20260.02101 · scoring model v2026.06.15
15 Jul 20260.02101
Show all 42 observations
24 Jan 20240.00103
8 Mar 20240.00656
13 Mar 20240.00724
19 Apr 20240.00591
3 Sep 20240.00497
16 Dec 20240.00510
17 Dec 20240.00525
22 Jan 20250.00709
17 Feb 20250.00842
17 Mar 20250.01323
29 Mar 20250.04115
30 Mar 20250.01323
15 Apr 20250.00188
16 Apr 20250.00196
16 May 20250.00188
20 May 20250.00237
29 May 20250.00196
6 Jun 20250.00267
7 Jun 20250.00295
8 Jun 20250.00267
12 Jun 20250.00255
8 Jul 20250.00267
11 Aug 20250.00337
18 Sep 20250.00322
1 Oct 20250.00255
3 Oct 20250.00267
4 Nov 20250.00383
6 Nov 20250.00483
18 Nov 20250.01882
21 Nov 20250.00483
18 Dec 20250.00462
25 Dec 20250.00383
28 Jan 20260.00483
18 Feb 20260.00366
19 Feb 20260.00383
25 Mar 20260.00483
24 May 20260.00415
29 May 20260.00462
11 Jun 20260.00383
15 Jun 20260.02101
27 Jun 20260.02084
15 Jul 20260.02101

42 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.02101Published2024-01-16Index as of2026-07-15

The record had been public for 2 years, 5 months when this index was last written.

Published 2024-01-16 receipt · Index as of 2026-07-15 derived

Siblings and hubs

Records related to this one

Its defect family

tianocore edk2

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-2023-45232.

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.