CVE-2024-6633
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 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. The 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.
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 confidenceFileCatalyst Workflow includes a deprecated HSQLDB for installation purposes. The default credentials for this embedded database are publicly documented in a vendor knowledgebase article. Attackers who can network-access the HSQLDB service can authenticate using these known default credentials to read, modify, or destroy application data, achieving critical-impact compromise of confidentiality, integrity, and availability.
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>= 5.0.4, < 5.1.7CVSS 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 FileCatalyst Workflow installationLocate the FileCatalyst Workflow installation directory, typically under the application's base path. Look for workflow server files or check installed programs list.Affected if FileCatalyst Workflow is installed on the system
-
Check installed version numberInspect the application's version file, about page, or run version check command from the installation directory. Compare against the affected range: 5.0.4 through 5.1.6.Affected if Installed version is 5.0.4 or higher but lower than 5.1.7
-
Determine if HSQLDB is in useCheck the database configuration file (typically in the configuration or conf directory) for HSQLDB connection strings or JDBC driver references. Look for hsqldb in connection URLs.Affected if HSQLDB is configured as the active database backend
-
Verify HSQLDB network accessibilityCheck network listening ports on the system. HSQLDB commonly listens on port 9001 or configured ports. Review firewall rules and application network binding configuration.Affected if HSQLDB port is exposed and accessible from network
-
Confirm default credentials are unchangedReview the database configuration file for HSQLDB credentials. Check if username/password match documented defaults or remain at factory settings.Affected if Default HSQLDB credentials have not been changed from documented defaults
Affected if FileCatalyst Workflow version 5.0.4-5.1.6 is running with HSQLDB accessible over the network using unchanged default credentials.
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.
dbcve · scoped5.1.7
Migrate FileCatalyst Workflow from the deprecated HSQLDB to a production-grade database (MySQL, PostgreSQL, Oracle, or SQL Server) following vendor documentation, or at minimum change the default HSQLDB credentials if HSQLDB usage is unavoidable.
5.1.7 or later
- Upgrade FileCatalyst Workflow to version 5.1.7 or later to remediate the default credentials vulnerability
- Alternatively, if upgrading is not immediately feasible, configure FileCatalyst Workflow to use an alternative database (such as PostgreSQL, MySQL, or Oracle) as recommended in the vendor documentation, instead of the deprecated HSQLDB
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6633 — 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-2024-6633 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