vciy

CVE-2024-29025

INDEX BUILT · 2026-10-18

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.

Netty HttpPostRequestDecoder can OOM

CVE-2024-290254 of 4 sources documented this
17

rank 17 = 0 + 13 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.01380  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from the CNA  ·  without this subject the record ranks 4

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 17

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

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

Hindsight · the state

0.0138EPSSNOT IN KEVas of 2026-10-18
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2025-03-28, 444 days at 0.01, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-770, allocation of resources without limits or throttling. The index holds 2602 prior instances of this class, 2 KEV-listed. taxonomy@v1

Full pattern panel

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

Running netty? 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

Watch netty

Set up a watchlist (free with an account: one stack of three products)

Record your call

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

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

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
ImpactPartial availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-770 Allocation of Resources Without Limits or Throttlingreceipt
Published consequencesCWE-770: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)cwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchnetty 4.1.108receipt
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.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

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 CNA5.3 MEDIUMreceipt
Exploit probability0.0138 · top 28% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byGitHub_Mreceipt
Recorded changes37 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productnettyreceipt
Published rangesnetty < 4.1.108; debian linux 10.0receipt

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.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$16,600over the next 30 days, if this record is yours
Movement-$147,000on 2025-03-28, the last material move, 1 year, 2 months before this reading
Basisassumeda published average, not your estate

$16,600 = $4.99M incident cost x 0.24048551839932833 exposure x 0.0138 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.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The `HttpPostRequestDecoder` can be tricked to accumulate data. While the decoder can store items on the disk if configured so, there are no limits to the number of fields the form can have, an attacher can send a chunked post consisting of many small fields that will be accumulated in the `bodyListHttpData` list. The decoder cumulates bytes in the `undecodedChunk` buffer until it can decode a field, this field can cumulate data without limits. This vulnerability is fixed in 4.1.108.Final. receipt

NVD's analysis a second authority

weakness
CWE-770
affected versions
netty < 4.1.108; debian linux 10.0
also scored by
security-advisories@github.com 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

check it yourself github.com github.com gist.github.com lists.debian.org receipt

Dated events

2025-03-27EPSS moved 0.00 to 0.132025-03-28EPSS moved 0.13 to 0.00

Movement the material steps

26 Mar 20240.00045
17 Mar 20250.00415 · scoring model v2025.03.14
27 Mar 20250.12677 · crossed 0.10
28 Mar 20250.00415 · crossed 0.10
15 Jun 20260.0138 · scoring model v2026.06.15

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

Show all 37 observations
26 Mar 20240.00045
17 Mar 20250.00415
19 Mar 20250.01408
20 Mar 20250.00415
27 Mar 20250.12677
28 Mar 20250.00415
29 Mar 20250.01408
30 Mar 20250.00415
15 Apr 20250.00133
3 May 20250.00056
8 May 20250.00048
15 May 20250.00056
10 Jun 20250.00048
15 Jun 20250.00056
10 Jul 20250.00048
16 Jul 20250.00049
29 Jul 20250.00048
20 Sep 20250.00093
23 Sep 20250.00245
18 Nov 20250.01046
21 Nov 20250.00245
28 Nov 20250.00283
1 Dec 20250.00245
4 Dec 20250.00261
1 Jan 20260.00225
4 Jan 20260.00261
1 Feb 20260.00225
4 Feb 20260.00261
1 Mar 20260.00225
4 Mar 20260.00261
20 Mar 20260.00268
2 Apr 20260.00261
9 Apr 20260.00268
13 Apr 20260.00324
5 May 20260.00316
6 May 20260.00343
15 Jun 20260.0138

37 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.0138Published2024-03-25Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.00415 → 0.01408) and the record had been public for 2 years, 2 months when this index was last written.

Published 2024-03-25 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-770, allocation of resources without limits or throttling. The index holds 2602 prior instances of this class, 2 KEV-listed. cwe-consequences@4.20

CVE-2020-3566 · Cisco IOS XR Softwarematches 6 of 9KEV listed · 2020receipt
CVE-2020-3569 · Cisco IOS XR Softwarematches 6 of 9KEV listed · 2020receipt

2602 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Its defect family

netty

Of the 9 records in this family that state one, this holds the highest EPSS percentile: 0.7025.

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

Family membership: held values

This record is one of a group, and the group's page describes all of them. 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-2024-29025.

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.