vciy

CVE-2003-0132

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 memory leak in Apache 2.0 through 2.0.44 allows remote attackers to cause a denial of service (memory consumption) via large chunks of linefeed…

CVE-2003-01323 of 4 sources documented this
37

rank 37 = 22 + 13 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.86677  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.0, from NVD  ·  without this subject the record ranks 24

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 37

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.24Mover the next 30 days, if this record is yours
Movement-$14,800on 2024-12-17, the last material move, 1 year, 8 months before this reading
Basisassumeda published average, not your estate

$1.24M = $4.99M incident cost x 0.28625080150224425 exposure x 0.86677 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.86677EPSSNOT IN KEVas of 2026-09-20
Severity5 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2023-11-08, 1015 days at 0.87, as of 2026-08-19. 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

Check a version against this record

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 authentication · low attack complexityreceipt
ImpactPartial availability lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classCWE-772 Missing Release of Resource after Effective Lifetimereceipt
Published consequencesCWE-772: Availability: DoS: Resource Consumption (Other), DoS: Resource Consumption (Memory), DoS: Resource Consumption (CPU)[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 19 Aug 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, NVD5 MEDIUMreceipt
Exploit probability0.86677 · top 0.27% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes23 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesApache http serverreceipt
Published rangesapache http server >= 2.0.0 <= 2.0.44receipt

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 memory leak in Apache 2.0 through 2.0.44 allows remote attackers to cause a denial of service (memory consumption) via large chunks of linefeed characters, which causes Apache to allocate 80 bytes for each linefeed. receipt

NVD's analysis a second authority

severity
5 AV:N/AC:L/Au:N/C:N/I:N/A:P
weakness
CWE-772
affected versions
apache http server >= 2.0.0 <= 2.0.44

check it yourself marc.info vupen.com marc.info idefense.com marc.info secunia.com +14 morereceipt

Dated events

2023-03-07EPSS moved 0.33 to 0.972025-10-28EPSS moved 0.81 to 0.87

Movement the material steps

4 Feb 20220.33043
7 Mar 20230.97267 · crossed 0.50 and 0.90 · scoring model v2023.03.01
17 Dec 20240.89202 · crossed 0.90
17 Mar 20250.86718 · scoring model v2025.03.14
15 Jun 20260.86677 · scoring model v2026.06.15
19 Aug 20260.86677
Show all 23 observations
4 Feb 20220.33043
7 Mar 20230.97267
12 Sep 20230.97184
8 Nov 20230.91966
30 Jan 20240.91799
11 Aug 20240.90240
17 Dec 20240.89202
17 Mar 20250.86718
29 Mar 20250.82578
30 Mar 20250.86718
30 Jul 20250.80961
1 Oct 20250.86718
27 Oct 20250.80961
28 Oct 20250.86718
2 Dec 20250.87752
10 Dec 20250.84592
14 Dec 20250.82248
27 Dec 20250.85951
28 Dec 20250.82248
13 Feb 20260.85004
15 Jun 20260.86677
12 Jul 20260.86179
19 Aug 20260.86677

23 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.86677Published2003-04-03Index as of2026-08-19

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

Published 2003-04-03 receipt · Index as of 2026-08-19 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2003-0132.

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.