Unauthenticated full device access via API
Published Sep 28, 2022 · Updated May 21, 2025
Missing authentication in UWP 3.0 before 8.5.0.3 and CPY before 2.8.3 allows remote attackers full device access. The API exposes critical device functions without checking a session or other authentication credential. No credentials or user interaction are required, and published sources do not identify the affected API endpoints or request forms.
Summary
What happened
Missing authentication in UWP 3.0 before 8.5.0.3 and CPY before 2.8.3 allows remote attackers full device access. The API exposes critical device functions without checking a session or other authentication credential. No credentials or user interaction are required, and published sources do not identify the affected API endpoints or request forms.
The record
- CVE
- CVE-2022-22526
- Published
- Sep 28, 2022
- Updated
- May 21, 2025
- Vendor
- Carlo Gavazzi AB
- Product
- UWP 3.0 Monitoring Gateway and Controller – EDP version
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 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=8 <8.5.0.3
What conditions does exploitation require?
What is affected?
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
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