Privilege escalation via unverified update repository
Published Apr 10, 2023 · Updated Feb 7, 2025
Repository authenticity failure in Pega Synchronization Engine 3.1.1 through 3.1.27 allows attackers to execute code via a malicious server. The client accepts update content from a redirected repository without verifying that the repository is an authentic Pega source. A man-in-the-middle position and compromised server configuration are required; trusted malicious content can run on the desktop and gain administrative access.
Summary
What happened
Repository authenticity failure in Pega Synchronization Engine 3.1.1 through 3.1.27 allows attackers to execute code via a malicious server. The client accepts update content from a redirected repository without verifying that the repository is an authentic Pega source. A man-in-the-middle position and compromised server configuration are required; trusted malicious content can run on the desktop and gain administrative access.
The record
- CVE
- CVE-2023-26467
- Published
- Apr 10, 2023
- Updated
- Feb 7, 2025
- Vendor
- Pegasystems Inc.
- Product
- Pega Synchronization Engine
- Classifications
- CWE-345, T1553
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2023CVE publishedPublication date reported by the CVE source.
- Feb 7, 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=3.1.1 <unspecified
- Affected versionversion=unspecified <3.1.28
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