Service interruption via unreleased process memory
Published Jan 11, 2021 · Updated Aug 5, 2024
Memory leak in K7TSMngr.exe in K7 Antivirus Premium 15.1.0.53 allows attackers to interrupt service through crafted internal-channel input. K7 identifies improper handling of that input but does not disclose which message or allocation path fails to release memory. Triggering requires access to an affected internal channel; published material limits the reported consequence to denial of service without specifying a hang or crash.
Summary
What happened
Memory leak in K7TSMngr.exe in K7 Antivirus Premium 15.1.0.53 allows attackers to interrupt service through crafted internal-channel input. K7 identifies improper handling of that input but does not disclose which message or allocation path fails to release memory. Triggering requires access to an affected internal channel; published material limits the reported consequence to denial of service without specifying a hang or crash.
The record
- CVE
- CVE-2018-11246
- Published
- Jan 11, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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