dbcve.org
Foxman UnApplication · Hitachienergy

CVE-2022-3929

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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-un: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:*:*:*:*:*:*:*

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FOXMAN-UN and UNEM products use CORBA (Common Object Request Broker Architecture) over TCP/IP without encryption for client-server communication. This allows network attackers to intercept and trace internal messages in plaintext, exposing sensitive operational data.

MitigationImplement TLS/SSL encryption for CORBA communications or migrate to a secure protocol to protect data in transit. Coordinate with Hitachi Energy for vendor-specific patches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Foxman UnApplication
Affected:< r16a
UnemApplication
Affected:< r16a

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product
    Determine whether the system has Hitachi Energy Foxman UN or UNEM installed. Check system inventory, installed software list, or product documentation.
    Affected if The product is Foxman UN or UNEM and version is below r16a
  2. Check the installed version
    Retrieve the product version number. This is typically available via the product's about panel, version command, or installation directory documentation.
    Affected if Version is earlier than r16a (r16a and later contain the fix)
  3. Verify CORBA communication is in use
    Identify whether CORBA-based client-server communication is configured and active. Check product documentation for CORBA module or service status.
    Affected if CORBA over TCP/IP is enabled and used for client-server communication
  4. Inspect CORBA transport encryption settings
    Examine the CORBA configuration files or transport layer settings to determine if TLS/SSL encryption is enabled for the communication channel.
    Affected if CORBA communications are configured without encryption (plaintext TCP/IP)
  5. Monitor network traffic
    Capture and inspect network traffic on the CORBA communication port to verify if data is transmitted in plaintext.
    Affected if Network traffic reveals unencrypted plaintext messages

The environment is affected if Foxman UN or UNEM version is below r16a AND CORBA over unencrypted TCP/IP is enabled for client-server communication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement TLS/SSL encryption for CORBA communications or migrate to a secure protocol to protect data in transit. Coordinate with Hitachi Energy for vendor-specific patches.

Recommended fix High confidence

FOXMAN-UN R16a or later; UNEM R16a or later

  1. Upgrade FOXMAN-UN to version R16a or later
  2. Upgrade UNEM to version R16a or later
  3. After upgrade, verify that CORBA communication is now encrypted

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Foxman Un Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
68.0 hours of engineering $12,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $19,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3929 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data