Credential disclosure via shared robot-file encryption key
Published Apr 11, 2025 · Updated Apr 11, 2025
Hard-coded key use in OPEN, Inc. BizRobo! all versions allows remote attackers to recover credentials from obtained robot files. The platform encrypts credential information embedded in every robot file with the same single cryptographic key rather than a per-deployment secret. Exploitation requires access to both a robot file and the shared key; the documented consequence is credential disclosure, not data modification or service interruption.
Summary
What happened
Hard-coded key use in OPEN, Inc. BizRobo! all versions allows remote attackers to recover credentials from obtained robot files. The platform encrypts credential information embedded in every robot file with the same single cryptographic key rather than a per-deployment secret. Exploitation requires access to both a robot file and the shared key; the documented consequence is credential disclosure, not data modification or service interruption.
The record
- CVE
- CVE-2025-31362
- Published
- Apr 11, 2025
- Updated
- Apr 11, 2025
- Vendor
- OPEN, Inc.
- Product
- BizRobo!
- Classifications
- CWE-321, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2025CVE publishedPublication date reported by the CVE source.
- Apr 11, 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=all versions
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