{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41400 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."},"fix_prompt":"Check this codebase for CVE-2022-41400 and fix it if it is affected.\n\nWhat it is: CVE-2022-41400 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.\nExploitation: There is no known exploitation of CVE-2022-41400 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-41400/ (Markdown: https://insights.sbomify.com/CVE-2022-41400/index.md)","id":"CVE-2022-41400","markdown":"https://insights.sbomify.com/CVE-2022-41400/index.md","name":"CVE-2022-41400","record":{"aliases":["GHSA-gh39-23rm-995j"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Sage 300 ERP","requires_auth":"none","summary":"Attackers can decrypt user passwords and SQL connection strings using a hard-coded key, leading to credential theft and database access.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sage_300","vendor":"sage"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Sage 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"OpenRefine Server-Side Request Forgery vulnerability","id":"CVE-2022-41401"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41399"},"products":["n/a"],"published":"2023-04-28","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41397","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2022-38583","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-45492","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41398","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41399","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2023-29927","kev_date_added":null,"published":"2023-05-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["n/a"]},"summary":"Attackers can decrypt user passwords and SQL connection strings using a hard-coded key, leading to credential theft and database access.","url":"https://insights.sbomify.com/CVE-2022-41400/"}