CVE-2022-3929

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.

Communication between the client and server partially using CORBA over TCP/IP

CVE-2022-39294 of 4 sources documented this

rank 29 = 0 + 25 + 0 + 4 + 0

rank@v1 · scheduled

Exploitation evidence0/40EPSS 0.00389

Someone is already using it

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

EPSS 0.00389 · without this subject the record ranks 29

Impact25/25CVSS 9.8, from NVD

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD · without this subject the record ranks 4

Movement0/15no persisting rise in 365 days

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

Blast radius4/102 products in the CPE ranges

How much of the world it touches

NVD CPE configurations

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

Obligation0/10no CISA due date

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$19,400over 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

$19,400 = $4.99M incident cost x 1 exposure x 0.00389 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

Severity8.3 HIGHreceipt

Harmtotal lossreceipt

Exploitationnone in held sources

Defensefix version namedreceipt

Movementscoring model changedreceipt

PLATEAUMinimal movement since 2023-01-06, 1256 days at 0.00, 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

Sources disagree here.

Severity score

Hitachi Energy8.3 HIGHreceipt

NVD9.8 CRITICALreceipt

What it costs

Hitachi EnergyComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt

NVDComplete confidentiality, integrity and availability lossreceipt

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

Running Hitachi Energy FOXMAN-UN? 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.

Accept Defer Patch by…Not affected Mitigated

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.

Reachreachable from an adjacent network · no privileges required · no user interaction · high attack complexityreceipt

ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt

Scored fromCVSS v3.1 · the CNA's vectorreceipt

Weakness classCWE-319 Cleartext Transmission of Sensitive Informationreceipt

Published consequencesCWE-319: Integrity, Confidentiality: Read Application Data, Modify Files or Directories; Integrity, Confidentiality: Read Application Data, Modify Files or Directories, Other[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inFOXMAN-UN R16A; UNEM R16Areceipt

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.3 HIGHreceipt

CVSS, NVD9.8 CRITICALreceipt

Exploit probability0.00389 · top 67% of all CVEsreceipt

Blast breadth2 products across 1 vendorderived

Assigned byHitachi Energyreceipt

Recorded changes20 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productHitachi Energy FOXMAN-UN; Hitachi Energy UNEMreceipt

Published rangeshitachienergy foxman-un < r16a; hitachienergy unem < r16areceipt

Fixed inFOXMAN-UN R16A; UNEM R16Areceipt

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.

Attack path

What it is stated by the CNA

Communication between the client and the server application of the affected products is partially done using CORBA (Common Object Request Broker Architecture) over TCP/IP. This protocol is not encrypted and allows tracing of internal messages. This issue affects * FOXMAN-UN product: FOXMAN-UN R15B, FOXMAN-UN R15A, FOXMAN-UN R14B, FOXMAN-UN R14A, FOXMAN-UN R11B, FOXMAN-UN R11A, FOXMAN-UN R10C, FOXMAN-UN R9C; * UNEM product: UNEM R15B, UNEM R15A, UNEM R14B, UNEM R14A, UNEM R11B, UNEM R11A, UNEM R10C, UNEM R9C. List of CPEs: * cpe:2.3:a:hitachienergy:foxman-un:R15B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R15A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-u receipt

Read the rest of the CNA's description

n:R14B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R14A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R11B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R11A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R10C:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:foxman-un:R9C:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R15B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R15A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R14B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R14A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R11B:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R11A:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R10C:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:unem:R9C:*:*:*:*:*:*:*

NVD's analysis a second authority

severity: 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness: CWE-319
affected versions: hitachienergy foxman-un < r16a; hitachienergy unem < r16a
also scored by: [email protected] 8.3 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

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

check it yourself search.abb.com search.abb.com receipt

Movement the material steps

6 Jan 20230.00885

7 Mar 20239.1e-4 · scoring model v2023.03.01

17 Mar 20250.00119 · scoring model v2025.03.14

15 Jun 20260.00389 · scoring model v2026.06.15

Show all 20 observations

6 Jan 20230.00885

7 Mar 20239.1e-4

8 Mar 20230.00091

6 Dec 20230.00105

12 Jan 20240.00166

7 Feb 20240.00187

17 Jun 20240.00214

28 Jul 20240.00221

17 Mar 20250.00119

29 Mar 20250.00113

30 Mar 20250.00119

30 Sep 20250.00132

1 Nov 20250.00141

18 Nov 20250.00261

21 Nov 20250.00141

7 Jan 20260.00194

11 Jan 20260.00243

13 Jan 20260.00242

19 Jan 20260.00261

15 Jun 20260.00389

20 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

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

Published 2023-01-05 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

No record cites this identifier and it carries no alias. The advisory that covers it is below.

Fixed with these, by one advisory

CVE-2021-40341 CVE-2021-40342 CVE-2022-3927 CVE-2022-3928

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

Every CVE we hold for Hitachi Added to CISA KEV this week The whole index

These are index-wide views, not findings about CVE-2022-3929.

What usually comes next

Brief on CVE-2022-3929Researched against the CNA's own sources, cited, print-ready. Needs an account.What moved across the whole index this week?The material set, not the catalogue.Do we run Hitachi Energy FOXMAN-UN?Match a product list against what we hold. Product names, not versions.

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.