# CVE-2022-41397: Hardcoded credentials in n/a

> Attackers can decrypt sensitive configuration and database secrets in Sage 300 Web Screens and Global Search features due to a hard-coded encryption key.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-r76m-38wv-wmv4

## What is CVE-2022-41397?

CVE-2022-41397 is a critical vulnerability in n/a, published on 28 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-41397?

It affects 1 product.


Products: Sage Sage 300.

## How do I fix CVE-2022-41397?

No fix has been published for CVE-2022-41397 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41397 being exploited?

There is no known exploitation of CVE-2022-41397 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-41400](https://insights.sbomify.com/CVE-2022-41400/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-38583](https://insights.sbomify.com/CVE-2022-38583/): Missing authorization in n/a (high 7.8)
- [CVE-2021-45492](https://insights.sbomify.com/CVE-2021-45492/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-41398](https://insights.sbomify.com/CVE-2022-41398/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2022-41399](https://insights.sbomify.com/CVE-2022-41399/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41397 and fix it if it is affected.

What it is: CVE-2022-41397 is a critical vulnerability in n/a, published on 28 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41397 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41397/ (Markdown: https://insights.sbomify.com/CVE-2022-41397/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41397
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41397
- OSV: https://osv.dev/vulnerability/CVE-2022-41397

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41397/
Summaries are generated and may contain mistakes; the official description above is the record.