Credential disclosure via hard-coded Blowfish key
Published Apr 28, 2023 · Updated Jan 30, 2025
Use of a hard-coded encryption key in Sage 300 through 2022 allows remote attackers to decrypt user passwords and SQL connection strings. The product uses one embedded 40-byte Blowfish key to encrypt and decrypt those values in ISAM database files kept in the shared data directory. Exploitation requires obtaining the affected files, and recovered credentials expose application accounts and database connections without changing stored data.
Summary
What happened
Use of a hard-coded encryption key in Sage 300 through 2022 allows remote attackers to decrypt user passwords and SQL connection strings. The product uses one embedded 40-byte Blowfish key to encrypt and decrypt those values in ISAM database files kept in the shared data directory. Exploitation requires obtaining the affected files, and recovered credentials expose application accounts and database connections without changing stored data.
The record
- CVE
- CVE-2022-41400
- Published
- Apr 28, 2023
- Updated
- Jan 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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.
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