Service interruption via HTTP proxy memory leak
Published Feb 12, 2020 · Updated Nov 15, 2024
A memory leak in Cisco IOS before 15.2(1)T allows remote attackers to exhaust memory through the HTTP PROXY Server process. The process fails to release memory while handling traffic when Cisco ISR Web Security uses Cisco ScanSafe with NTLM user authentication. The affected features must be configured; memory exhaustion can interrupt device service without disclosing or altering data.
Summary
What happened
A memory leak in Cisco IOS before 15.2(1)T allows remote attackers to exhaust memory through the HTTP PROXY Server process. The process fails to release memory while handling traffic when Cisco ISR Web Security uses Cisco ScanSafe with NTLM user authentication. The affected features must be configured; memory exhaustion can interrupt device service without disclosing or altering data.
The record
- CVE
- CVE-2011-4661
- Published
- Feb 12, 2020
- Updated
- Nov 15, 2024
- Vendor
- ClamAV
- Product
- Cisco IOS
- Classifications
- CWE-772, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Nov 15, 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=before 15.2(1)T
What conditions does exploitation require?
What is affected?
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