CVE Vulnerabilities

CVE-2023-1711

Improper Output Neutralization for Logs

Published: May 30, 2023 | Modified: Nov 21, 2024
CVSS 3.x
4.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

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

The product does not neutralize or incorrectly neutralizes output that is written to logs.

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

This can allow an attacker to forge log entries or inject malicious content into logs. Log forging vulnerabilities occur when:

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References