vciy

CVE-2012-0192

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.

Multiple integer overflows in vclmi.dll in the visual class library module in IBM Lotus Symphony before 3.0.1 might allow remote attackers to execute…

CVE-2012-01923 of 4 sources documented this
29

rank 29 = 1 + 23 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.05137  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.3, from NVD  ·  without this subject the record ranks 6

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

4 products in the CPE ranges  ·  without this subject the record ranks 24

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$256,000over the next 30 days, if this record is yours
Movement-$114,000on 2026-02-27, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$256,000 = $4.99M incident cost x 1 exposure x 0.05137 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.05137EPSSNOT IN KEVas of 2026-09-20
Severity9.3 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2025-09-23, 349 days at 0.05, as of 2026-09-07. 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 authenticationreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classCWE-189receipt
Published consequencesMITRE publishes no common consequences for this weakness.[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 7 Sep 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, NVD9.3 CRITICALreceipt
Exploit probability0.05137 · top 8% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byibmreceipt
Recorded changes14 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesIbm lotus symphonyreceipt
Published rangesibm lotus symphony <= 3.0.0.3; ibm lotus symphony 1.3; ibm lotus symphony 3.0.0.1; ibm lotus symphony 3.0.0.2receipt

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

Multiple integer overflows in vclmi.dll in the visual class library module in IBM Lotus Symphony before 3.0.1 might allow remote attackers to execute arbitrary code via an embedded (1) JPEG or (2) PNG image object in a Symphony document that triggers a heap-based buffer overflow, as demonstrated by a .doc file. receipt

NVD's analysis a second authority

severity
9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
weakness
CWE-189
affected versions
ibm lotus symphony <= 3.0.0.3; ibm lotus symphony 1.3; ibm lotus symphony 3.0.0.1; and 1 more, listed in full below

check it yourself securityfocus.com secunia.com osvdb.org exchange.xforce.ibmcloud.com www-01.ibm.com receipt

Dated events

2024-02-11EPSS moved 0.08 to 0.112026-02-27EPSS moved 0.11 to 0.09

Movement the material steps

4 Feb 20220.06309
7 Mar 20230.07676 · scoring model v2023.03.01
11 Feb 20240.11022 · crossed 0.10
17 Mar 20250.14857 · scoring model v2025.03.14
27 Feb 20260.08597 · crossed 0.10
15 Jun 20260.05203 · scoring model v2026.06.15
7 Sep 20260.05137
Show all 14 observations
4 Feb 20220.06309
7 Mar 20230.07676
11 Feb 20240.11022
12 Sep 20240.12055
1 Nov 20240.12211
17 Mar 20250.14857
19 Mar 20250.15682
29 Mar 20250.1166
30 Mar 20250.15682
23 Sep 20250.11953
14 Dec 20250.10875
27 Feb 20260.08597
15 Jun 20260.05203
7 Sep 20260.05137

14 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.05137Published2012-01-23Index as of2026-09-07

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

Published 2012-01-23 receipt · Index as of 2026-09-07 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2012-0192.

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.