CVE Vulnerabilities


Improper Encoding or Escaping of Output

Published: May 30, 2023 | Modified: Jun 06, 2023
CVSS 3.x
CVSS 2.x

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:::::::*


The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

Affected Software

Name Vendor Start Version End Version
Foxman_un Hitachienergy r9c (including) r9c (including)
Foxman_un Hitachienergy r10c (including) r10c (including)
Foxman_un Hitachienergy r11a (including) r11a (including)
Foxman_un Hitachienergy r11b (including) r11b (including)
Foxman_un Hitachienergy r14a (including) r14a (including)
Foxman_un Hitachienergy r14b (including) r14b (including)
Foxman_un Hitachienergy r15a (including) r15a (including)
Foxman_un Hitachienergy r15b (including) r15b (including)
Foxman_un Hitachienergy r16a (including) r16a (including)
Unem Hitachienergy r9c (including) r9c (including)
Unem Hitachienergy r10c (including) r10c (including)
Unem Hitachienergy r11a (including) r11a (including)
Unem Hitachienergy r11b (including) r11b (including)
Unem Hitachienergy r14a (including) r14a (including)
Unem Hitachienergy r14b (including) r14b (including)
Unem Hitachienergy r15a (including) r15a (including)
Unem Hitachienergy r15b (including) r15b (including)
Unem Hitachienergy r16a (including) r16a (including)

Extended Description

Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead. Most products follow a certain protocol that uses structured messages for communication between components, such as queries or commands. These structured messages can contain raw data interspersed with metadata or control information. For example, “GET /index.html HTTP/1.1” is a structured message containing a command (“GET”) with a single argument ("/index.html") and metadata about which protocol version is being used (“HTTP/1.1”). If an application uses attacker-supplied inputs to construct a structured message without properly encoding or escaping, then the attacker could insert special characters that will cause the data to be interpreted as control information or metadata. Consequently, the component that receives the output will perform the wrong operations, or otherwise interpret the data incorrectly.

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.
  • Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
  • If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
  • For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.