Credential theft via improper certificate validation
Published Sep 23, 2022 · Updated May 22, 2025
Improper certificate validation in Velneo vClient 28.1.3 allows man-in-the-middle attackers to obtain user credentials. By default, the client accepts a VATPS connection without automatically verifying that the presented vServer certificate is authentic. The attack requires access to the victim's network and user interaction, and the reported consequence is credential disclosure.
Summary
What happened
Improper certificate validation in Velneo vClient 28.1.3 allows man-in-the-middle attackers to obtain user credentials. By default, the client accepts a VATPS connection without automatically verifying that the presented vServer certificate is authentic. The attack requires access to the victim's network and user interaction, and the reported consequence is credential disclosure.
The record
- CVE
- CVE-2021-45035
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Velneo
- Product
- Velneo vClient
- Classifications
- CWE-295, CWE-287, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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=28.1.3
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