Malicious file execution via unquoted service path
Published Feb 17, 2020 · Updated Aug 4, 2024
Unquoted service path handling in McAfee DXL Broker 5.0.x through 5.0.2 and 6.0.x through 6.0.0 allows local users to execute files. The Windows service configuration leaves an executable path containing spaces unquoted, so Windows can resolve a carefully named executable earlier in the path instead of the broker binary. A local user must have high privileges, place the crafted executable, and induce service execution; successful exploitation runs that file or interrupts the service.
Summary
What happened
Unquoted service path handling in McAfee DXL Broker 5.0.x through 5.0.2 and 6.0.x through 6.0.0 allows local users to execute files. The Windows service configuration leaves an executable path containing spaces unquoted, so Windows can resolve a carefully named executable earlier in the path instead of the broker binary. A local user must have high privileges, place the crafted executable, and induce service execution; successful exploitation runs that file or interrupts the service.
The record
- CVE
- CVE-2020-7252
- Published
- Feb 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- McAfee
- Product
- Data Exchange Layer (DXL) Broker
- Classifications
- CWE-428, CWE-250, T1574.009
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=5.0.x <=5.0.2
- Affected versionversion=6.0.x <=6.0.0
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