iterm2: Improper Output Neutralization for Logs
CVE-2023-46321 is a critical-severity improper output neutralization for logs vulnerability in iterm2, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.5 as the first without the flaw, so updating iterm2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update iterm2 to 3.5 or a later version.
- Read the advisory on iterm2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Output Neutralization for Logs
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
How developers prevent this class of flaw
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
More Improper Output Neutralization for Logs vulnerabilities (CWE-117)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- gitlab.com/gnachman/iterm2/-/commit/de3d351e1bd3bc1c1a4f85fe976c592e497dd071Third Party Advisory
Other vulnerabilities in iterm2
- 8.7 High severity
- 7.8 High severity
- 9.3 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.