CVE-2022-41400
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSage 300 through 2022 uses a hard-coded 40-byte blowfish key to encrypt and decrypt user passwords and SQL connection strings stored in ISAM database files in the shared data directory. This issue could allow attackers to decrypt user passwords and SQL connection strings.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSage 300 through 2022 uses a hard-coded 40-byte Blowfish key embedded in the software binary to encrypt and decrypt user passwords and SQL connection strings stored in ISAM database files in the shared data directory. Anyone with access to the software can extract this key from the binary and decrypt all stored credentials, enabling unauthorized access to the application and underlying SQL databases.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2022CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Sage 300 installation and versionCheck the installed Sage 300 version using the program's About dialog, installation directory metadata, or Windows Add/Remove Programs. Look for version indicators in the installation folder (typically under C:\Sage\ or C:\Program Files\Sage).Affected if The installed version is Sage 300 2022 or any earlier version (<= 2022)
-
Locate ISAM database files in shared data directorySearch for .dbf or ISAM database files in the common Sage 300 data directory (commonly found under the application data folder or a shared network location configured during setup).Affected if ISAM database files containing user passwords and SQL connection strings exist in the Sage data directory
-
Check binary for hard-coded encryption keyExamine the Sage 300 executable binaries (such as accpac.exe or related DLLs) for a 40-byte Blowfish key pattern. Use a hex editor or binary analysis tool to search for cryptographic key structures within the compiled binaries.Affected if A hard-coded 40-byte Blowfish key is present in the software binary
-
Verify access control on data directoryReview file system permissions on the Sage 300 shared data directory. Check which users and groups have read access to the ISAM database files and configuration files.Affected if Multiple users or non-admin accounts have read access to the ISAM files containing stored credentials
If Sage 300 version 2022 or earlier is installed and ISAM database files exist in an accessible shared directory, the environment is affected by this hard-coded key vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataOrganizations should contact Sage for an official patch that implements proper key management. In the interim, restrict physical and network access to the Sage data directory, monitor for unauthorized access to the ISAM files, and consider rotating affected SQL credentials as a precautionary measure.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41400 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data