vciy

CVE-2010-4056

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.

solid.exe in IBM solidDB 6.5.0.3 and earlier does not properly perform a recursive call to a certain function upon receiving packet data containing a…

CVE-2010-40563 of 4 sources documented this
25

rank 25 = 2 + 13 + 0 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.08430  ·  without this subject the record ranks 23

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 12

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 25

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

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

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

$120,000 = $4.99M incident cost x 0.28625080150224425 exposure x 0.0843 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.0843EPSSNOT IN KEVas of 2026-09-20
Severity5 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2022-02-04, 1592 days at 0.08, as of 2026-06-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

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 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, NVD5 MEDIUMreceipt
Exploit probability0.0843 · top 5% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes9 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesIbm soliddbreceipt
Published rangesibm soliddb <= 6.5.0.3; ibm soliddb 4.5.167; ibm soliddb 4.5.168; ibm soliddb 4.5.169receipt
Show all 20 published ranges
ibm soliddb <= 6.5.0.3
ibm soliddb 4.5.167
ibm soliddb 4.5.168
ibm soliddb 4.5.169
ibm soliddb 4.5.173
ibm soliddb 4.5.175
ibm soliddb 4.5.176
ibm soliddb 4.5.178
ibm soliddb 6.0.1060
ibm soliddb 6.0.1061
ibm soliddb 6.0.1064
ibm soliddb 6.0.1065
ibm soliddb 6.0.1066
ibm soliddb 6.1
ibm soliddb 6.1.20
ibm soliddb 6.3.33
ibm soliddb 6.3.37
ibm soliddb 6.5.0.0
ibm soliddb 6.5.0.1
ibm soliddb 6.5.0.2

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

solid.exe in IBM solidDB 6.5.0.3 and earlier does not properly perform a recursive call to a certain function upon receiving packet data containing a single integer field, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a TCP session on port 1315. receipt

NVD's analysis a second authority

severity
5 AV:N/AC:L/Au:N/C:N/I:N/A:P
affected versions
ibm soliddb <= 6.5.0.3; ibm soliddb 4.5.167; ibm soliddb 4.5.168; and 17 more, listed in full below

check it yourself exchange.xforce.ibmcloud.com exploit-db.com vupen.com secunia.com securitytracker.com aluigi.altervista.org receipt

Dated events

2025-03-29EPSS moved 0.10 to 0.132025-03-30EPSS moved 0.13 to 0.10

Movement the material steps

4 Feb 20220.01319
7 Mar 20230.02874 · scoring model v2023.03.01
17 Mar 20250.09672 · scoring model v2025.03.14
29 Mar 20250.12991 · crossed 0.10
30 Mar 20250.09672 · crossed 0.10
15 Jun 20260.0843 · scoring model v2026.06.15
Show all 9 observations
4 Feb 20220.01319
7 Mar 20230.02874
2 May 20240.02282
17 Dec 20240.05667
17 Mar 20250.09672
29 Mar 20250.12991
30 Mar 20250.09672
1 Jul 20250.08775
15 Jun 20260.0843

9 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.0843Published2010-10-22Index as of2026-06-15

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

Published 2010-10-22 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

advisory published by secunia.com

Of the 3 records in this advisory that state one, this holds the highest EPSS percentile: 0.94616.

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2010-4056.

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.