{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6633 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6633 is a critical vulnerability in Fortra FileCatalyst Workflow, published on 27 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6633 and fix it if it is affected.\n\nWhat it is: CVE-2024-6633 is a critical vulnerability in Fortra FileCatalyst Workflow, published on 27 Aug 2024. 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-2024-6633 in the wild and no public exploit code.\n\nAffected product: Fortra FileCatalyst Workflow. 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-2024-6633/ (Markdown: https://insights.sbomify.com/CVE-2024-6633/index.md)","id":"CVE-2024-6633","markdown":"https://insights.sbomify.com/CVE-2024-6633/index.md","name":"CVE-2024-6633","record":{"aliases":["GHSA-g79x-6jx3-7f7g"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"FileCatalyst Workflow","requires_auth":"none","summary":"Attackers can access the deprecated HSQLDB using published default credentials, compromising data confidentiality and integrity if the database is reachable.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Fortra","cpe":[{"product":"filecatalyst_workflow","vendor":"fortra"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","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"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The default credentials for the setup HSQL database (HSQLDB) for FileCatalyst Workflow are published in a vendor knowledgebase article. Misuse of these credentials could lead to a compromise of confidentiality, integrity, or availability of the software.\n\nThe HSQLDB is only included to facilitate installation, has been deprecated, and is not intended for production use per vendor guides. However, users who have not configured FileCatalyst Workflow to use an alternative database per recommendations are vulnerable to attack from any source that can reach the HSQLDB.","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":"Insecure Default in FileCatalyst Workflow 5.1.6 Build 139 (and earlier)","id":"CVE-2024-6633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Master Currency WP","id":"CVE-2024-6634"},"packages":[],"prev":{"headline":"SQL Injection in FileCatalyst Workflow 5.1.6 Build 139 (and earlier)","id":"CVE-2024-6632"},"products":["FileCatalyst Workflow"],"published":"2024-08-27","related":[{"cvss_score":9.8,"headline":"SQL Injection Vulnerability in FileCatalyst Workflow 5.1.6 Build 135 (and earlier)","id":"CVE-2024-5276","kev_date_added":null,"published":"2024-06-25"},{"cvss_score":9.8,"headline":"Remote Code Execution in FileCatalyst Workflow 5.x prior to 5.1.6 Build 114","id":"CVE-2024-25153","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":7.2,"headline":"SQL Injection in FileCatalyst Workflow 5.1.6 Build 139 (and earlier)","id":"CVE-2024-6632","kev_date_added":null,"published":"2024-08-27"}],"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-08-29","vendors":["Fortra"]},"summary":"Attackers can access the deprecated HSQLDB using published default credentials, compromising data confidentiality and integrity if the database is reachable.","url":"https://insights.sbomify.com/CVE-2024-6633/"}