Appliance compromise via exposed firmware-signing key
Published Mar 5, 2025 · Updated Nov 3, 2025
Firmware verification in Vasion Print Virtual Appliance Host before 1.0.750 and Application before 20.0.1442 lets attackers compromise appliances. The unauthenticated /va-api update route accepts signatures derived from MS_AUTH_KEY, while that key is stored in appliance.env and exposed to numerous appliance containers. Access to the key through that file or an affected container enables a malicious image to be uploaded and installed without administrator credentials.
Summary
What happened
Firmware verification in Vasion Print Virtual Appliance Host before 1.0.750 and Application before 20.0.1442 lets attackers compromise appliances. The unauthenticated /va-api update route accepts signatures derived from MS_AUTH_KEY, while that key is stored in appliance.env and exposed to numerous appliance containers. Access to the key through that file or an affected container enables a malicious image to be uploaded and installed without administrator credentials.
The record
- CVE
- CVE-2025-27680
- Published
- Mar 5, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1105
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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
- Firmware update API 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