Malicious driver acceptance via insufficient antivirus protection
Published Mar 5, 2025 · Updated Mar 5, 2025
Insufficient antivirus protection in Vasion Print before Application 20.0.1923 allows remote attackers to supply malicious drivers. The public record identifies driver antivirus handling as the locus but does not disclose the scanner or validation routine that fails to reject known malicious code. Network access without authentication is sufficient, and acceptance of a managed malicious driver creates a path for attacker-supplied code to reach client endpoints.
Summary
What happened
Insufficient antivirus protection in Vasion Print before Application 20.0.1923 allows remote attackers to supply malicious drivers. The public record identifies driver antivirus handling as the locus but does not disclose the scanner or validation routine that fails to reject known malicious code. Network access without authentication is sufficient, and acceptance of a managed malicious driver creates a path for attacker-supplied code to reach client endpoints.
The record
- CVE
- CVE-2025-27665
- Published
- Mar 5, 2025
- Updated
- Mar 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-693
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Mar 5, 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?
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
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