CVE-2022-41397
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 · uneditedThe optional Web Screens and Global Search features for Sage 300 through version 2022 use a hard-coded 40-byte blowfish key ("LandlordPassKey") to encrypt and decrypt secrets stored in configuration files and in database tables.
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 versions 2022 and prior with optional Web Screens and Global Search features use a hard-coded 40-byte Blowfish key ('LandlordPassKey') to encrypt and decrypt secrets stored in configuration files and database tables. This hard-coded key is now public knowledge via the CVE, allowing any attacker to decrypt all sensitive data protected by this key without authentication.
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 versionLocate the Sage 300 installation directory (commonly C:\Sage\Sage300\). Check the version by opening the About screen in the application or locating a version file in the installation folder.Affected if The installed version is 2022 or any version prior to 2022.
-
Verify Web Screens feature is installedCheck if the Web Screens module is present by looking for the Web Screens folder in the Sage 300 installation directory or checking the feature list in Sage 300 Application Server configuration.Affected if Web Screens feature is installed and enabled on the system.
-
Verify Global Search feature is installedCheck if the Global Search module is present by looking for Global Search components in the Sage 300 installation directory or checking the feature list in Sage 300 Application Server configuration.Affected if Global Search feature is installed and enabled on the system.
-
Search for the hard-coded encryption keySearch configuration files (INI, XML, CONFIG files) in the Sage 300 data and program directories for the string 'LandlordPassKey'. Also check database tables that store configuration or user preference data for this string in encrypted form.Affected if The hard-coded key 'LandlordPassKey' is found in any configuration file or database field used by Sage 300.
The environment is affected if Sage 300 version 2022 or prior is installed with either the Web Screens or Global Search feature enabled, and the hard-coded Blowfish key 'LandlordPassKey' is present in configuration files or database tables.
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 dataUpdate to a patched version of Sage 300 that removes the hard-coded key, implement proper secret management, and re-encrypt all affected configuration files and database fields with a unique, securely-managed encryption key.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.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 $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41397 — 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-41397 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