Vulnerabilities > Improper Output Neutralization for Logs
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2025-03-20 | CVE-2024-9606 | Improper Output Neutralization for Logs vulnerability in Litellm In berriai/litellm before version 1.44.12, the `litellm/litellm_core_utils/litellm_logging.py` file contains a vulnerability where the API key masking code only masks the first 5 characters of the key. | 7.5 |
| 2025-02-20 | CVE-2024-49355 | Improper Output Neutralization for Logs vulnerability in IBM Openpages With Watson 9.0 IBM OpenPages with Watson 8.3 and 9.0 may write improperly neutralized data to server log files when the tracing is enabled per the System Tracing feature. | 6.5 |
| 2025-01-28 | CVE-2025-0754 | The vulnerability was found in OpenShift Service Mesh 2.6.3 and 2.5.6. | 4.3 |
| 2025-01-25 | CVE-2024-35150 | IBM Maximo Application Suite 8.10.12, 8.11.0, 9.0.1, and 9.1.0 - Monitor Component does not neutralize output that is written to logs, which could allow an attacker to inject false log entries. | 5.3 |
| 2025-01-07 | CVE-2024-52891 | Improper Output Neutralization for Logs vulnerability in IBM Concert Software IBM Concert Software 1.0.0, 1.0.1, 1.0.2, 1.0.2.1, and 1.0.3 could allow an authenticated user to inject malicious information or obtain information from log files due to improper log neutralization. | 5.4 |
| 2024-08-30 | CVE-2024-8334 | Improper Output Neutralization for Logs vulnerability in Master-Nan Sweet-Cms A vulnerability was found in master-nan Sweet-CMS up to 5f441e022b8876f07cde709c77b5be6d2f262e3f. | 8.1 |