dbcve.org
Sage 300Application · Sage

CVE-2022-41399

HIGH · 7.5 CVSS v3.1 Published 2023-04-28
Fix available
A fix is available. Upgrade to after 2022 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The optional Web Screens feature for Sage 300 through version 2022 uses a hard-coded 40-byte blowfish key ("PASS_KEY") to encrypt and decrypt the database connection string for the PORTAL database found in the "dbconfig.xml". This issue could allow attackers to obtain access to the SQL database.

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 · moderate confidence

The Sage 300 Web Screens feature uses a hard-coded 40-byte Blowfish key ('PASS_KEY') to encrypt and decrypt database connection strings stored in the dbconfig.xml file for the PORTAL database. An attacker with access to this configuration file can decrypt the credentials using the known static key, gaining unauthorized access to the SQL database.

MitigationReplace the hard-coded Blowfish key with a secure key management solution (e.g., hashicorp vault, Azure Key Vault, or encrypted environment variables), rotate all exposed database credentials, and restrict access to the dbconfig.xml file to prevent credential theft.

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
Sage 300Application
Affected:<= 2022

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Sage 300 installation and version
    Open Windows Control Panel > Programs and Features, look for 'Sage 300' and note the installed version. The affected version is 2022 and earlier.
    Affected if The installed Sage 300 version is 2022 or earlier (any version up to and including 2022).
  2. Locate the dbconfig.xml file
    Navigate to the Sage 300 Web Screens installation directory, typically found in the 'Web' subfolder. Look for a file named 'dbconfig.xml' in the PORTAL or configuration directories.
    Affected if The dbconfig.xml file exists in the Sage 300 Web Screens installation directory.
  3. Inspect dbconfig.xml for encrypted connection strings
    Open the dbconfig.xml file in a text editor. Look for XML elements containing encrypted or base64-encoded strings that represent database connection credentials (such as SQL Server connection strings with passwords).
    Affected if The dbconfig.xml file contains encrypted database connection strings, particularly for the PORTAL database.
  4. Verify the Web Screens feature is in use
    Check if the Sage 300 Web Screens component is enabled and configured. Look for IIS application pools or web services related to Sage 300 in Windows Services or IIS Manager.
    Affected if The Sage 300 Web Screens web component is installed and configured, making the dbconfig.xml file accessible.

You are affected if Sage 300 version 2022 or earlier is installed with the Web Screens feature enabled and a dbconfig.xml file containing encrypted database connection strings exists in the installation directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2022
Interim mitigation

Replace the hard-coded Blowfish key with a secure key management solution (e.g., hashicorp vault, Azure Key Vault, or encrypted environment variables), rotate all exposed database credentials, and restrict access to the dbconfig.xml file to prevent credential theft.

Recommended fix Moderate confidence

Sage 300 version 2023 or later (contact Sage for specific fixed release)

  1. Verify the current Sage 300 installation version and confirm the Web Screens feature is enabled
  2. Contact Sage technical support to confirm the availability of a patched release for version 2022 or later that addresses CVE-2022-41399
  3. If a patched version is available, obtain the update from Sage's official download portal or through your authorized Sage partner
  4. Before applying the update, perform a full backup of the Sage 300 database and configuration files, including the dbconfig.xml file
  5. Apply the Sage update following the official Sage upgrade documentation
  6. After updating, verify that the Web Screens feature no longer uses the hard-coded Blowfish key for database connection string encryption
  7. If a patched version is not yet available, review Sage knowledge base articles for any interim configuration mitigations or patches
Caveat Review Sage 300 release notes for version 2023 for any compatibility changes or configuration requirements when upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sage 300 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41399 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41399 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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