Unspecified impact via mishandled DECRQSS response
Published Nov 23, 2022 · Updated Apr 25, 2025
Improper input validation in iTerm2 before 3.4.18 allows remote attackers to cause unspecified impact via a DECRQSS response. The vendor says the DECRQSS response was changed to close a security hole but has not published the faulty parser operation or malformed input condition. Reachability requires an attacker-controlled response, while public vendor material does not identify the resulting consequence.
Summary
What happened
Improper input validation in iTerm2 before 3.4.18 allows remote attackers to cause unspecified impact via a DECRQSS response. The vendor says the DECRQSS response was changed to close a security hole but has not published the faulty parser operation or malformed input condition. Reachability requires an attacker-controlled response, while public vendor material does not identify the resulting consequence.
The record
- CVE
- CVE-2022-45872
- Published
- Nov 23, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo