Unauthenticated internal API access via exposed Docker bridge
Published Sep 29, 2025 · Updated Sep 29, 2025
Missing authentication in Vasion Print VA/SaaS components before 25.2.169 and 25.2.1518 allows remote attackers to access internal APIs. Unrestricted firewall rules route traffic into the 172.17.0.0/16 Docker bridge, where container APIs accept requests without authentication, ACLs, or a client identifier. Network reachability to the deployment is sufficient to expose credentials and configuration and to support remote code execution through reachable internal services.
Summary
What happened
Missing authentication in Vasion Print VA/SaaS components before 25.2.169 and 25.2.1518 allows remote attackers to access internal APIs. Unrestricted firewall rules route traffic into the 172.17.0.0/16 Docker bridge, where container APIs accept requests without authentication, ACLs, or a client identifier. Network reachability to the deployment is sufficient to expose credentials and configuration and to support remote code execution through reachable internal services.
The record
- CVE
- CVE-2025-34221
- Published
- Sep 29, 2025
- Updated
- Sep 29, 2025
- Vendor
- Vasion
- Product
- Vasion Print Application
- Classifications
- CWE-306, CAPEC-1, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2025CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=* <25.2.1518
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
- Unauthenticated Docker container API access demonstrationproof 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