vciy

CVE-2003-0131

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.

The SSL and TLS components for OpenSSL 0.9.6i and earlier, 0.9.7, and 0.9.7a allow remote attackers to perform an unauthorized RSA private key…

CVE-2003-01313 of 4 sources documented this
29

rank 29 = 2 + 19 + 0 + 8 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.06280  ·  without this subject the record ranks 27

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 10

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 29

How much of the world it touches

NVD CPE configurations

11 products in the CPE ranges  ·  without this subject the record ranks 21

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$202,000over the next 30 days, if this record is yours
Movement+$581,000on 2024-12-17, the last material move, 1 year, 5 months before this reading
Basisassumeda published average, not your estate

$202,000 = $4.99M incident cost x 0.6442432101309884 exposure x 0.0628 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.0628EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
STEADY10Holding near 0.06 across 18 observations. 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 confidentiality, integrity and availability lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

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 Jun 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, NVD7.5 HIGHreceipt
Exploit probability0.0628 · top 7% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesOpensslreceipt
Published rangesopenssl 0.9.6; openssl 0.9.6a; openssl 0.9.6b; openssl 0.9.6creceipt
Show all 11 published ranges
openssl 0.9.6
openssl 0.9.6a
openssl 0.9.6b
openssl 0.9.6c
openssl 0.9.6d
openssl 0.9.6e
openssl 0.9.6g
openssl 0.9.6h
openssl 0.9.6i
openssl 0.9.7
openssl 0.9.7a

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

The SSL and TLS components for OpenSSL 0.9.6i and earlier, 0.9.7, and 0.9.7a allow remote attackers to perform an unauthorized RSA private key operation via a modified Bleichenbacher attack that uses a large number of SSL or TLS connections using PKCS #1 v1.5 padding that cause OpenSSL to leak information regarding the relationship between ciphertext and the associated plaintext, aka the "Klima-Pokorny-Rosa attack." receipt

NVD's analysis a second authority

severity
7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
affected versions
openssl 0.9.6; openssl 0.9.6a; openssl 0.9.6b; and 8 more, listed in full below

check it yourself debian.org redhat.com redhat.com marc.info eprint.iacr.org oval.cisecurity.org +14 morereceipt

Dated events

2024-12-17EPSS moved 0.05 to 0.232026-06-15EPSS moved 0.18 to 0.06

Movement the material steps

4 Feb 20220.07559
7 Mar 20230.03347 · scoring model v2023.03.01
17 Dec 20240.23461 · crossed 0.10
17 Mar 20250.23158 · scoring model v2025.03.14
15 Jun 20260.0628 · crossed 0.10 · scoring model v2026.06.15
Show all 18 observations
4 Feb 20220.07559
7 Mar 20230.03347
5 Apr 20230.05378
8 Feb 20240.07419
29 Jul 20240.05378
17 Dec 20240.23461
17 Mar 20250.23158
29 Mar 20250.31466
30 Mar 20250.23158
16 Jul 20250.16267
30 Jul 20250.17249
1 Oct 20250.16267
27 Oct 20250.17249
28 Oct 20250.16267
27 Dec 20250.17249
28 Dec 20250.16267
31 Jan 20260.17937
15 Jun 20260.0628

18 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.0628Published2003-03-21Index as of2026-06-15

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

Published 2003-03-21 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.