vciy

CVE-2022-32142

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.

CODESYS runtime system prone to denial of service due to use of out of range pointer

CVE-2022-321424 of 4 sources documented this
18

rank 18 = 0 + 14 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.01053  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from NVD  ·  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 18

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$46,300over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$46,300 = $4.99M incident cost x 0.8814887365328109 exposure x 0.01053 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.01053EPSSNOT IN KEVas of 2026-09-20
Severity8.1 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementsteadyreceipt
PLATEAU10Minimal movement since 2022-06-25, 1538 days at 0.01, as of 2026-09-10. 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

Sources disagree here.

Severity score
CERTVDE8.1 HIGHreceipt
NVD5.5 MEDIUMreceipt
Scoring standard
CERTVDECVSS v3.1receipt
NVDCVSS v2.0receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running CODESYS Runtime Toolkit? 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

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 · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-823 Use of Out-of-range Pointer Offsetreceipt
Published consequencesCWE-823: Confidentiality: Read Memory; Availability: DoS: Crash, Exit, or Restart; Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands, Modify Memory[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchplcwinnt 2.4.7.57; runtime toolkit 2.4.7.57receipt
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, the CNA8.1 HIGHreceipt
CVSS, NVD5.5 MEDIUMreceipt
Exploit probability0.01053 · top 37% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byCERTVDEreceipt
Recorded changes23 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productCODESYS Runtime Toolkit; CODESYS PLCWinNTreceipt
Published rangescodesys plcwinnt >= 2.0 < 2.4.7.57; codesys runtime toolkit >= 2.0 < 2.4.7.57receipt

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.

Attack path

Network requestrequires low privilegesCODESYS PLCWinNTCWE-823 weaknessIntegrity and availability lossI:H / A:Hexploits CWE-823data compromise

What it is stated by the CNA

Multiple CODESYS Products are prone to a out-of bounds read or write access. A low privileged remote attacker may craft a request with invalid offset, which can cause an out-of-bounds read or write access, resulting in denial-of-service condition or local memory overwrite, which can lead to a change of local files. User interaction is not required. receipt

NVD's analysis a second authority

severity
5.5 AV:N/AC:L/Au:S/C:N/I:P/A:P
weakness
CWE-823
affected versions
codesys plcwinnt >= 2.0 < 2.4.7.57; codesys runtime toolkit >= 2.0 < 2.4.7.57
also scored by
[email protected] 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

The CNA scored it 8.1 and NVD 5.5. Both are shown because both were published; we do not pick one.

check it yourself customers.codesys.com receipt

Movement the material steps

25 Jun 20220.01055
7 Mar 20236.8e-4 · scoring model v2023.03.01
17 Mar 20250.00423 · scoring model v2025.03.14
15 Jun 20260.00899 · scoring model v2026.06.15
10 Sep 20260.01053
Show all 23 observations
25 Jun 20220.01055
7 Mar 20236.8e-4
8 Mar 20230.00068
25 May 20230.00079
1 Jul 20230.00124
15 Jan 20240.00158
17 Dec 20240.00051
17 Mar 20250.00423
19 Mar 20250.0047
29 Mar 20250.00439
30 Mar 20250.0047
20 Apr 20250.00501
28 Jun 20250.00369
29 Jun 20250.00388
5 Jul 20250.00363
9 Jul 20250.01065
13 Jul 20250.0103
18 Oct 20250.00787
15 Jun 20260.00899
21 Jun 20260.00977
11 Jul 20260.01001
18 Aug 20260.01022
10 Sep 20260.01053

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.01053Published2022-06-24Index as of2026-09-10

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

Published 2022-06-24 receipt · Index as of 2026-09-10 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

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-2022-32142.

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.