Privileged code execution via forgeable update checksums
Published Sep 12, 2022 · Updated Aug 3, 2024
Improper update validation in FreshService Agents before 2.11.0, 4.2.0, or 3.3.0 allows man-in-the-middle attackers to execute code. FreshAgent derives update approval values from an embedded secret and salt, allowing a forged checksum to validate a substituted package. An attacker must control the agent's network path; the scheduled update daemon runs the package as root on macOS and Linux or SYSTEM on Windows.
Summary
What happened
Improper update validation in FreshService Agents before 2.11.0, 4.2.0, or 3.3.0 allows man-in-the-middle attackers to execute code. FreshAgent derives update approval values from an embedded secret and salt, allowing a forged checksum to validate a substituted package. An attacker must control the agent's network path; the scheduled update daemon runs the package as root on macOS and Linux or SYSTEM on Windows.
The record
- CVE
- CVE-2022-36174
- Published
- Sep 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-354, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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
- FreshService forged-update proof of conceptproof of concept · demonstrated
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