HTTP response splitting via unsanitized input
Published Nov 3, 2022 · Updated Oct 25, 2024
HTTP response splitting in Cisco Secure Email and Secure Email and Web Manager allows remote attackers to inject headers into responses. Cisco identifies no affected endpoint or parameter; it states only that the application or environment fails to sanitize input before forming HTTP responses. Exploitation requires user interaction and lets unauthenticated remote attackers control a response body or split one response into multiple responses.
Summary
What happened
HTTP response splitting in Cisco Secure Email and Secure Email and Web Manager allows remote attackers to inject headers into responses. Cisco identifies no affected endpoint or parameter; it states only that the application or environment fails to sanitize input before forming HTTP responses. Exploitation requires user interaction and lets unauthenticated remote attackers control a response body or split one response into multiple responses.
The record
- CVE
- CVE-2022-20772
- Published
- Nov 3, 2022
- Updated
- Oct 25, 2024
- Vendor
- ClamAV
- Product
- Cisco Secure Email
- Classifications
- CWE-113
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2022CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.5.1-277
- Affected versionversion=14.0.0-698
- Affected versionversion=14.2.0-620
What conditions does exploitation require?
What is affected?
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