Process memory corruption via undisclosed network input
Published Jun 17, 2022 · Updated Apr 15, 2025
Memory corruption in BitTorrent Limited µTorrent allows remote attackers to corrupt process memory via unspecified network input. The published record does not identify the affected component, input field, or memory operation that mishandles attacker-controlled data. The attack requires user interaction but no authentication; the record does not distinguish a process crash from code execution.
Summary
What happened
Memory corruption in BitTorrent Limited µTorrent allows remote attackers to corrupt process memory via unspecified network input. The published record does not identify the affected component, input field, or memory operation that mishandles attacker-controlled data. The attack requires user interaction but no authentication; the record does not distinguish a process crash from code execution.
The record
- CVE
- CVE-2018-25042
- Published
- Jun 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- BitTorrent Limited
- Product
- µTorrent
- Classifications
- CWE-119, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
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
- Project Zero µTorrent proof of conceptproof of concept · unverified
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