Cyber Resilience

CVE-2023-46321

Iterm2 ≤ 3.4.21

Published
23 October 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0066 48th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2023-46321 is a critical-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Iterm2 Iterm2. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell metacharacters for a /usr/bin/man command line.

CWE(s)
NVD-CWE-noinfoCWE-117

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-46322Same product: Iterm2 Iterm2
CVE-2023-46300Same product: Iterm2 Iterm2
CVE-2025-22275Same product: Iterm2 Iterm2
CVE-2023-46301Same product: Iterm2 Iterm2
CVE-2024-38396Same product: Iterm2 Iterm2
CVE-2024-38395Same product: Iterm2 Iterm2
CVE-2026-41253Same product: Iterm2 Iterm2
CVE-2024-52962Shared CWE-117
CVE-2024-7696Shared CWE-117
CVE-2025-0754Shared CWE-117

Affected Assets

iterm2
iterm2
3.5.0 · ≤ 3.4.21

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

AU-1 Policy and Procedures
addresses: CWE-117

Policy and procedures require sanitization and neutralization when generating audit logs to avoid injection issues.

SI-15 Information Output Filtering
addresses: CWE-117

Requiring output to conform to expected content prevents unneutralized data from reaching logs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.28 Secure coding partial match
prevents

Secure coding practices mandate input validation and output encoding, directly preventing log injection.

References