# CVE-2023-1711: Information disclosure in FOXMAN-UN

> Attackers can obtain confidential information from logging components in systems using remote authentication.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-g6j4-f6g3-wmcx

## What is CVE-2023-1711?

CVE-2023-1711 is a medium-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability exists in a FOXMAN-UN and UNEM logging component, it only affects systems that use remote authentication to the network elements. 
If exploited an attacker could obtain confidential information.

List of CPEs:
  *  cpe:2.3:a:hitachienergy:foxman_un:R9C:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman_un:R10C:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R11A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R11B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R14A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R14B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R15A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R15B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman_un:R16A:*:*:*:*:*:*:*

  *  
  *  cpe:2.3:a:hitachienergy:unem:R9C:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy: unem :R10C:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R11A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R11B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R14A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R14B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R15A:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R15B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy: unem :R16A:*:*:*:*:*:*:*

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2023-1711?

It affects 2 products.


Products: Hitachienergy Foxman-Un, Hitachienergy Unem.

## How do I fix CVE-2023-1711?

No fix has been published for CVE-2023-1711 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1711 being exploited?

There is no known exploitation of CVE-2023-1711 in the wild and no public exploit code.

## Other vulnerabilities in Hitachi Energy FOXMAN-UN

- [CVE-2024-2013](https://insights.sbomify.com/CVE-2024-2013/): Auth bypass in FOXMAN-UN (critical 10.0)
- [CVE-2024-2012](https://insights.sbomify.com/CVE-2024-2012/): Auth bypass in FOXMAN-UN (critical 9.1)
- [CVE-2024-2011](https://insights.sbomify.com/CVE-2024-2011/): Memory corruption in FOXMAN-UN (high 8.6)
- [CVE-2022-3929](https://insights.sbomify.com/CVE-2022-3929/): Communication between the client and server partially using CORBA over TCP/IP (high 8.3)
- [CVE-2024-28020](https://insights.sbomify.com/CVE-2024-28020/): Hardcoded credentials in FOXMAN-UN (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1711 and fix it if it is affected.

What it is: CVE-2023-1711 is a medium-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-1711 in the wild and no public exploit code.

Affected product: Hitachi Energy FOXMAN-UN. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1711/ (Markdown: https://insights.sbomify.com/CVE-2023-1711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1711
- OSV: https://osv.dev/vulnerability/CVE-2023-1711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1711/
Summaries are generated and may contain mistakes; the official description above is the record.